| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
Common Manifest File Options
The manifest file includes information related to processing your data and returning your storage device. The following table explains options that are common to all manifest files.
| Option | Description | Required |
|---|---|---|
| accessKeyId |
The Access Key ID of the person responsible for paying for the data transfer. For more information about the Access Key ID, go to Security Credentials. The The following is an example of accessKeyId: Type: String Default: None | Yes |
| deviceId |
Your storage device's serial number or other unique identifier. If your device
does not have a unique number, please place a sticker with its own
unique identifier onto the device and then enter that identifier as the
deviceId: MyCompany489732 Type: String Default: None | Yes |
| generator |
A field describing the application that put together the manifest file and
submitted the generator: AWS Import/Export Sample App 1.0 Type: String Default: None | No |
| logBucket |
The Amazon S3 bucket where AWS Import/Export saves your log. You must create a bucket
before we can save log data to it; we do not create the bucket for you.
Your account ( Note For import to Amazon EBS, if your storage device’s capacity exceeds 1TB, a device image is stored as two or more objects to your specified Amazon S3 log bucket. logBucket: logging-bucket Type: String Default: The import Constraints: Must be an existing Amazon S3 bucket name | Yes, except for import to Amazon S3. |
| logPrefix |
A string to insert between the bucket name and log report name to prevent name
collisions. For more information, go to Preventing Log File Name Collisions. The following is an example of a
logPrefix: logs/ Type: String Default: None | No |
| manifestVersion |
The version of the manifest specification used to write the manifest file. The manifest version must be 2.0 for import and export to Amazon S3 and 3.0 for import to Amazon EBS and Amazon Glacier. Type: String Default: None Valid Values: 2.0 | 3.0 | Yes |
| notificationEmail |
A semicolon delimited list of email addresses to which you want us to send job completed notification emails. notificationEmail: joe.random@noreply.com Type: String Default: None | No |
| returnAddress | The address we return your storage device to after completing the job. The returnAddress option includes subfields, as shown in the following example.
returnAddress:
name: John Doe
company: Amazon
street1: 123 Any Street
city: Shenzhen
stateOrProvince: Nanshan
postalCode: 518054
phoneNumber: 555-555-0100
country: China
The subfields Type: String Default: None Constraints: Your return address must be a physical street address and not a post office box. | Yes |
|
serviceLevel |
The service level for the job. For more information about specifying your job’s service levels, go to Expediting the Return of Your Storage Device. serviceLevel: expeditedShipping Type: String Default: standard Valid Values: standard | expeditedShipping | No |
Example Import to Amazon S3 Manifest Using Common Options
The following example is the manifest file content for an import job showing most of
the common manifest file options, including expedited shipping. It also includes the
bucket option and the eraseDevice option
because they required for Amazon S3 manifest files.
manifestVersion: 2.0
accessKeyId:
bucket: data-load-bucket
deviceId: ABCDE
generator: AWS ImportExport Web Service Tool 1.0
logPrefix: logs
logBucket: iemanifest-log-bucket
prefix: imported/
eraseDevice: no
notificationEmail: john.doe@example.com;jane.doe@example.com
returnAddress:
name: Joe Random
company: Amazon Web Services
street1: 123 Any Street
city: Anytown
stateOrProvince: WA
postalCode: 91111
phoneNumber: 555-555-0100
country: USA
serviceLevel: expeditedShipping 
