|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
These options are common to Amazon S3, Amazon EBS, and Amazon Glacier import jobs.
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.
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.
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
eraseDevice: yes notificationEmail: firstname.lastname@example.org
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.
For example, if your job ID is 53TX4, the log file is saved to
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
logs the log file key your key would become
logsimport-log-jobId instead of
cannot be longer than 1024 bytes. If it is, AWS Import/Export returns an
InvalidManifestField error from the