AWS Import/Export
Developer Guide (API Version 2010-06-03)
« PreviousNext »
View the PDF for this guide.Go to the AWS Discussion Forum for this product.Go to the Kindle Store to download this guide in Kindle format.Did this page help you?  Yes | No |  Tell us about it...

Configuring Common Import Manifest Options

These options are common to Amazon S3, Amazon EBS, and Amazon Glacier import jobs.

For a complete list of manifest options, see Manifest File Options Reference. For examples of import manifest options, see Configuring Common Import Manifest Options.

Shipping Devices Internationally

When shipping devices internationally except within the European Union you must include the customs option in the manifest. For more information about the customs related manifest options, see Customs Manifest File Option.

Expediting the Return of Your Storage Device

When returning your device to a U.S. address from a U.S. region bucket, you can use the serviceLevel manifest option to upgrade your shipping. The default serviceLevel option is standard shipping, which includes free ground domestic shipping. When you specify expeditedShipping, your device is delivered using two-day shipping for an additional fee. For information about return shipping fees and services, go to the AWS Import/Export Calculator.

Specifying Device Erase After Import

After every import operation, even if the import was not successful, AWS Import/Export will erase the contents of your storage device to safeguard the data during return shipment. AWS overwrites all writable blocks on your device with zeros. You will need to repartition and format your device after we return it to you. You must include eraseDevice: Yes in your import manifest to acknowledge that your device will be erased. If we are unable to erase the data on the device, we will schedule it for destruction and our support team will contact you using the email address specified in the manifest file notificationEmail field.

eraseDevice: yes
notificationEmail: john.doe@example.com

Preventing Log File Name Collisions

The AWS Import/Export process generates a log file. The log file name always ends with the phrase import-log- followed by your JobId. There is a remote chance that you already have an object with this name. To avoid a key collision, you can add an optional prefix to the log file by adding the logPrefix option in the manifest. AWS Import/Export takes the string value specified for this option and inserts it between the bucket name and log report name. The following manifest option sets the prefix for the log key.

logPrefix: logs/

For example, if your job ID is 53TX4, the log file is saved to http://s3.amazonaws.com/mybucket/logs/import-log-53TX4.

Note

We do not include a forward slash (/) automatically. If you don't include the slash at the end of the value for logPrefix, the value is concatenated to the log file name. For example, if your logPrefix is logs the log file key your key would become logsimport-log-jobId instead of logs/import-log-JobId.

logPrefix + import-log-JOBID cannot be longer than 1024 bytes. If it is, AWS Import/Export returns an InvalidManifestField error from the CreateJob action.