AWS Import/Export
Developer Guide

Creating Amazon S3 Export Jobs

An Amazon S3 export transfers individual objects from Amazon S3 buckets to your device, creating one file for each object. You can export from more than one bucket and you can specify which files to export using manifest file options.


You cannot export Amazon S3 objects that have been transitioned to Amazon Glacier Storage Class using Amazon S3 Object Lifecycle Management. Before sending an Amazon S3 export job, check your lifecycle configuration rules to ensure that your objects will be available in Amazon S3 standard class until the export is complete. For more information, see Object Lifecycle Management in the Amazon S3 Developer Guide.

You must submit a separate job request for each device.

For more information, see Guidelines and Limitations

Amazon S3 Export Process

Export Job Process

1 You create an export manifest file that specifies how to load data onto your device, including an encryption PIN code or password and details such as the name of the bucket that contains the data to export. For more information, see The Export Manifest File. If you are going to mail us multiple storage devices, you must create a manifest file for each storage device.

You initiate an export job by sending a CreateJob request that includes the manifest file. You must submit a separate job request for each device. Your job expires after 30 days. If you do not send a device, there is no charge.

You can send a CreateJob request using the AWS Import/Export Tool, the AWS Command Line Interface (CLI), the AWS SDK for Java, or the AWS REST API. The easiest method is the AWS Import/Export Tool. For details, see

Sending a CreateJob Request Using the AWS Import/Export Web Service Tool

Sending a CreateJob Request Using the AWS SDK for Java

Sending a CreateJob Request Using the REST API


AWS Import/Export sends a response that includes a job ID, a signature value, and information on how to print your pre-paid shipping label. The response also saves a SIGNATURE file to your computer.

You will need this information in subsequent steps.


You copy the SIGNATURE file to the root directory of your storage device. You can use the file AWS sent or copy the SignatureFileContents values from the response into a new text file named SIGNATURE. The file name must be SIGNATURE, and the file must be in the device's root directory.

Each device you send must include the unique SIGNATURE file for that device and that JOBID. AWS Import/Export validates the SIGNATURE file on your storage device before starting the data load. If the SIGNATURE file is missing invalid (if, for instance, it is associated with a different job request), AWS Import/Export will not perform the data load and we will return your storage device. As in the following example.

**************************************** * SignatureFileContents * **************************************** version:2.0 signingMethod:HmacSHA1 jobId:QTEST signature:cbfdUuhhmauYS+ABCl5R9heDK/V=
5 Generate, print, and attach the pre-paid shipping label to the exterior of your package. See Shipping Your Storage Device for information on how to get your pre-paid shipping label.
6 You ship the device and cables to AWS through UPS. Make sure to include your job ID on the shipping label and on the device you are shipping. Otherwise, your job might be delayed. Your job expires after 30 days. If we receive your package after your job expires, we will return your device. You will only be charged for the shipping fees, if any.

You must submit a separate job request for each device.


You can send multiple devices in the same shipment. If you do, however, there are specific guidelines and limitations that govern what devices you can ship and how your devices must be packaged. If your shipment is not prepared and packed correctly, AWS Import/Export cannot process your jobs. Regardless of how many devices you ship at one time, you must submit a separate job request for each device. For complete details about packaging requirements when shipping multiple devices, see Shipping Multiple Devices.


AWS Import/Export validates the signature on the root drive of your storage device. If the signature doesn't match the signature from the CreateJob response, AWS Import/Export can’t load your data.

Once your storage device arrives at AWS, your data transfer typically begins by the end of the next business day. The time line for exporting your data depends on a number of factors, including the availability of an export station, the amount of data to export, and the data transfer rate of your device.


AWS reformats your device and encrypts your data using the PIN code or password you provided in your manifest.

9 We repack your storage device and ship it to the return shipping address listed in your manifest file. We do not ship to post office boxes.
10 You use your PIN code or TrueCrypt password to decrypt your device. For more information, see Encrypting Your Data

On this page: