Get Started with AWS for Free

Create a Free Account
Or Sign In to the Console

Receive twelve months of access to the AWS Free Usage Tier and enjoy AWS Basic Support features including, 24x7x365 customer service, support forums, and more.

Please note that AWS Import/Export is not currently available on the AWS Free Usage Tier.

Q. What is AWS Import/Export?

AWS Import/Export accelerates moving large amounts of data into and out of AWS using portable storage devices for transport. AWS transfers your data directly onto and off of storage devices using Amazon’s high-speed internal network and bypassing the Internet. For significant data sets, AWS Import/Export is often faster than Internet transfer and more cost effective than upgrading your connectivity.

Q. What can I do with AWS Import/Export?

AWS Import/Export makes it easy to quickly transfer large amounts of data into and out of Amazon Web Services. You can use AWS Import/Export for:

  • Data Migration – If you have data you need to upload into the AWS cloud for the first time, AWS Import/Export is often much faster than transferring that data via the Internet.
  • Content Distribution – Send data to your customers on portable storage devices.
  • Direct Data Interchange – If you regularly receive content on portable storage devices from your business associates, you can have them send it directly to AWS for import into EBS snapshots, Amazon Glacier archives, or your Amazon S3 buckets.
  • Offsite Backup – Send full or incremental backups to Amazon S3, Amazon Glacier, or Amazon EBS for reliable and redundant offsite storage.
  • Disaster Recovery – In the event you need to quickly retrieve a large backup stored in Amazon S3 or Amazon Glacier, use AWS Import/Export to transfer the data to a portable storage device and deliver it to your site.

Q. Which Amazon S3 Regions does AWS Import/Export support?

AWS Import/Export supports buckets stored in the US Standard, US West (Oregon), US West (Northern California), EU (Ireland), and Asia Pacific (Singapore) Regions.

Q. Which Amazon EBS Regions does AWS Import/Export support?

AWS Import/Export supports imports to Amazon EBS in the US East, US West (Oregon), US West (Northern California), EU (Ireland), and Asia Pacific (Singapore) Regions.

Q. Which Amazon Glacier Regions does AWS Import/Export support?

AWS Import/Export supports imports to Amazon Glacier in the US East, US West (Oregon), and US West (Northern California) and EU (Ireland) Regions.

Q. Where are my data loads performed?

When you create your job AWS will provide you with the AWS ship-to address based on your job’s region. Data loads in the US Standard Region buckets are sent to an AWS address in either the Pacific Northwest or Northern Virginia. Data loads in the US East (Virginia) Region are sent to an AWS address in Northern Virginia. Data loads in the US West (Oregon) and US West (Northern California) Regions are sent to an AWS address in the Pacific Northwest. Data loads in the EU (Ireland) Region are sent to an AWS address in Ireland. Data loads in the Asia Pacific (Singapore) Region are sent to an AWS address in Singapore.

When you ship your device, it will be delivered to a sorting facility, and then forwarded on to an AWS data center. The data load will start after the device is received at the data center.

Q. How can I get started with AWS Import/Export?

You can create your fist job within minutes by following the steps in the Getting Started section of our developer guide.

Q. When should I consider using AWS Import/Export?

If loading your data over the network would take 7 days or more, then you should consider using AWS Import/Export. To determine the best case for loading your data over the network use this formula:Number of Days = (Total Bytes)/(Megabits per second * 125 * 1000 * Network Utilization * 60 seconds * 60 minutes * 24 hours)

For example if you have a T1 connection (1.544Mbps) and 1TB (1024 * 1024 * 1024 * 1024 bytes) to move in or out of AWS the theoretical minimum time it would take to load over your network connection at 80% network utilization is 82 days.

Available Internet Connection Theoretical Min. Number of Days to Transfer 1TB at 80% Network Utilization When to Consider AWS Import/Export?
T1 (1.544Mbps) 82 days 100GB or more
10Mbps 13 days 600GB or more
T3 (44.736Mbps) 3 days 2TB or more
100Mbps 1 to 2 days 5TB or more
1000Mbps Less than 1 day 60TB or more

Q. How long does it take to load my data?

If your package arrives in the morning, AWS typically begins loading your data the same business day. Data loading time is then primarily governed by the device. Customers with high-performance SATA hard drives and eSATA devices have achieved rates well over 100 MB/sec. For estimates regarding data loading speeds and cost see the AWS Import/Export Calculator.

Q. Which additional factors influence Amazon S3 data loading speeds?

Data loads into and out of Amazon S3 require interaction with the device’s file system. As a result, average file size, number of files per directory, and file system type also impact data loading performance. Small files and very high numbers of files per directory tend to increase data loading times. For estimates regarding data loading speeds and cost see the AWS Import/Export Calculator.

Q. Are my data loads logged?

Yes. Details of each data load performed with AWS Import/Export are logged to an Amazon S3 bucket. You specify this Amazon S3 log bucket in your Create Job request, and must have permission to write to it.

Q. How much data can I load?

The total amount of data you can load using AWS Import/Export is limited only by the capacity of the devices that you send to AWS.

For Amazon EBS imports, if your storage device is less than or equal to the maximum volume size of 1TB, its contents will be loaded directly into an Amazon EBS snapshot. If your storage device’s capacity exceeds 1TB, a device image will be stored within your specified Amazon S3 log bucket. You can then create a RAID of EBS volumes using software such as Logical Volume Manager, and copy the image from Amazon S3 to this new volume.

For Amazon S3, individual files will be loaded as objects in Amazon S3, and may range up to 5 terabytes in size. Objects which are downloaded from Amazon S3 to your storage device may be limited by the maximum file size of your file system.

For Amazon Glacier, individual devices will be loaded as a single archive, and may range up to 4 terabytes in size. A 2TB device that only contains 500GB of data will still be uploaded to Glacier as a single 2TB archive (disk image).


Q. How will I be charged and billed for my use of AWS Import/Export?

With AWS Import/Export, you pay only for the resources that you use. Pricing is per device, data-loading-hour, and package shipped. Partial data-loading-hours are billed as full hours. Return shipping charges are dependent on your chosen AWS region, your return shipping destination, and your job’s shipping service level. There is no Data Transfer charge for data transferred between AWS Import/Export and Amazon. Usage for Amazon S3, Amazon Glacier, and Amazon EBS are billed separately from AWS Import/Export.

For AWS Import/Export pricing information, please visit the AWS Import/Export pricing page. For Amazon S3 pricing information, please visit the Amazon S3 pricing page. For Amazon EBS pricing information, please visit the Amazon EBS section of the Amazon EC2 pricing page. For Amazon Glacier pricing information, please visit the Amazon Glacier pricing page.

Q. What other charges am I responsible for?

You are responsible for purchasing your storage device(s) and the shipping charges to AWS (including any applicable duty and taxes). Packages with unpaid duty and/or taxes will be refused. If your data load is performed in the US Standard, US East (Virginia), US West (Oregon), or US West (Northern California) Region, you will also be responsible for any applicable duty and taxes on return shipments sent to addresses outside of the US. If your data load is performed in the Asia Pacific (Singapore) Region, you will also be responsible for any applicable duty and taxes on return shipments sent to addresses outside of Singapore. These duty and taxes will be charged directly by our return shipping carrier upon delivery of your package.

Q. When will I be billed for my use of AWS Import/Export?

The device fee is charged when your package arrives at AWS. The data-loading-hour billing starts once AWS Import/Export begins transferring data to or from your storage device. If there are any interruptions to the data load, you will not be charged during the period of interruption. Any applicable return shipping expenses will be charged once your package is ready for shipment to your return shipping address.

Q. What am I charged for return shipping?

Return shipping expenses vary depending on your return shipping destination, your job’s shipping service level, and the location of your Amazon S3 bucket:

US Standard, US East (Virginia), US West (Oregon), and US West (Northern California) Regions

  • If you have specified a return address within the US, AWS will pay reasonable return shipping charges, but you will be responsible for any return shipping expenses that AWS determines to be unreasonable or excessive.
  • If you have specified a return address outside of the US or expedited shipping, or special shipment is required, shipping charges based on your shipment destination, shipment type and weight will apply.

EU (Ireland) Region

  • If you have specified a return address within Ireland, AWS will pay reasonable return shipping charges, but you will be responsible for any return shipping expenses that AWS determines to be unreasonable or excessive.
  • If you have specified a return address outside of Ireland, or special shipment is required, shipping charges based on your shipment destination, shipment type and weight will apply. . At this time, devices shipped to AWS for import into or export from EU (Ireland) Region buckets must originate from and be returned to an address within the European Union.

Asia Pacific (Singapore) Region

  • If you have specified a return address within Singapore, AWS will pay reasonable return shipping charges, but you will be responsible for any return shipping expenses that AWS determines to be unreasonable or excessive.
  • If you have specified a return address outside of Singapore, or special shipment is required, shipping charges based on your shipment destination, shipment type and weight will apply.

To estimate your return shipping charges, please refer to the AWS Import/Export Calculator. PO Boxes are not a valid return shipping address.


Q. What do I need to get started using the service?

You can use the open source AWS Import/Export command line application, a third party tool, or program directly against the web service interface.

Q. What do I need to get started developing against the service?

If you intend to build an application to create and manage AWS Import/Export jobs, then you should download the AWS SDK for Java or AWS SDK for .NET, and the open source AWS Import/ Export command line application. You can use one of the AWS SDKs or program directly against the web service. To learn more about the web service API refer to the AWS Import/Export API Guide.

Q. Do jobs expire?

Yes, if AWS has not received your storage device within 30 days of job creation, the job will automatically be canceled. AWS will not accept packages for canceled jobs.

Q. Can a job have more than one storage device?

No, each job is associated with exactly one Create Job request and one customer device. If your data spans multiple devices, you must create multiple jobs.

Q. Can I enclose multiple jobs in the same package?

Yes, you can ship multiple jobs/devices in one package. For more information, please refer to the documentation for Shipping Multiple Devices.

Q. What will happen if I ship my device to the wrong AWS data loading facility?

AWS cannot process devices sent to a data loading facility in the wrong region. The data loading facilities are region specific. If you ship your device to the wrong AWS address, AWS will return your package to you without performing the data load. AWS does not ship devices that might contain data not encrypted by AWS. We will erase the device before returning it. You should then reload your data and ship your device to the correct AWS address. You will be responsible for any applicable return shipping charges and device-handling fees.

Q. Can I upgrade my return shipping?

Yes, AWS Import/Export supports expedited shipping for imports into and exports from US Region buckets that will be returned to a US address. If you set the serviceLevel field to expeditedShipping, after completing the data load your device will be delivered via 2-day shipping. For additional information regarding return shipping fees and services, please refer to the AWS Import/Export Calculator.

Q. What locations does AWS accept shipping from?

For imports into and exports from US Standard, US West (Oregon), US West (Northern California), and Asia Pacific (Singapore) Region buckets, AWS accepts packages from all countries, except those that are listed as under embargo by the US or countries not serviced by DHL, our international return shipping carrier in the US and Singapore. For imports into and exports from EU (Ireland) Region buckets, AWS accepts packages from all countries within the European Union.

Q. Can I ship my package from one address and have it returned to another address?

Yes, you can ship your package to AWS from one address and have it returned to another address.

Q. Are there specific device and content regulations for shipments to or from the US?

If you are importing or exporting from the US Standard, US East (Virginia), US West (Oregon), or US West (Northern California) regions and are shipping your device from or requesting that AWS return your device to a non-US based address, you must include the AWS USCustoms fields when submitting your request and your shipment must comply with the following US and international import and export regulations:

  1. The import and export of your device and/or data should not require a license under the regulations of any applicable country, including the United States Export Administration Regulations or the International Traffic in Arms Regulations. Only devices and data that are classified as EAR99 under US Export Administration Regulations and are not subject to the International Traffic in Arms Regulations are eligible for AWS Import/Export.
  2. The import and export of your device and/or data should not be prohibited by the regulations of any applicable country, including the United States Export Administration Regulations or the International Traffic in Arms Regulations.
  3. If the data on your device contains encryption software, then the software must be properly classified as 5D992 under US Export Administration Regulations (please confirm classification with the software manufacturer).
  4. Only devices valued at less than US $2,500 are eligible for AWS Import/Export.

Q. Are there specific device and content regulations for shipments to or from Singapore?

If you are importing or exporting from the Asia Pacific (Singapore) Region and are shipping your device from or requesting that AWS return your device to a non-Singapore based address, you must include the AWS Customs fields when submitting your request. Additionally your shipment must comply with the following:

  1. The import and export of your device and data is not prohibited by, and does not require license, notice, or approval under, the regulations of any applicable country, including Singapore and the United States.
  2. The import and export of your device and data is not prohibited by, subject to, and does not require license, notice, or approval under, the International Traffic in Arms Regulations.
  3. If your device or data contain encryption software or other technology, you must properly classify the technology under the regulations of any applicable countries, and such technology must not require license, notice or approval under any applicable regulations.
  4. Only devices valued at less than US $2,500 are eligible for AWS Import/Export.
  5. If you are shipping your device into Singapore from a non-Singapore address, but returning your device to a Singapore address, you must have a business establishment or fixed establishment inside Singapore.

Q. Can I cancel a job?

Yes, you can cancel a job any time before we start the data load, however you will be charged the device handling feel when we receive your device. To cancel a job, submit a Cancel Job request specifying the corresponding JOBID. AWS does not ship devices that might contain data not encrypted by AWS. Once the device is at AWS, the data on the device will be erased and it will be returned to the Return Address specified with the Create Job request. If you need to change your Return Shipping Address make sure to submit an Update Job prior to Cancel Job request. You will incur any applicable return shipping charges if you cancel a job after you have shipped your device to us.

Q. Can I receive data from 3rd parties through AWS Import/Export?

Yes, if the 3rd party is already signed up for Amazon S3 you can grant their AWS account write access on your bucket. They would then follow the normal AWS Import/Export data loading procedures. Alternatively, you could create an import job, and securely provide the 3rd party with your SIGNATURE file or (for Amazon Glacier and Amazon EBS) barcode, and instructions for packing and shipping a storage device to AWS Import/Export. If the SIGNATURE becomes compromised, AWS recommends that you cancel the job and create a new one. A compromised SIGNATURE would allow someone else to load data to the location specified in your manifest file.

Q. Do I need to backup my data before sending it to AWS?

Yes, you should always have another copy of your data before shipping your device to AWS. Your device and data could be damaged or lost in transit. In addition, we finalize import jobs by erasing all data on the device. Please keep your backup copy until you confirm that your data is uploaded successfully.


Q. How do I load my data into Amazon EBS?

To import data to Amazon EBS, start by loading your data onto a storage device, such as an external USB or eSATA hard drive. Then submit a Create Job request, which includes your target Amazon EBS region and return shipping address. You’ll receive back shipping instructions in a PDF.

Print out the PDF, and cut off the barcode at the bottom of the sheet. Tape the barcode to your device, and package it along with any necessary cables. Then ship the package to the address specified in the shipping instructions.

After we load your data to Amazon EBS, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request. PO Boxes are not a valid return shipping address. For more information about the Create Job process, please refer to the AWS Import/Export Developer Guide.

Q. What happens to my device after the import job is completed?

After we import data from your device, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request.

Q. Do I need an Amazon S3 bucket to load data into Amazon EBS?

AWS Import/Export requires that you specify an Amazon S3 bucket that your account has write permission on for storing data loading logs. This log bucket is also used in the event that the device you send exceeds the Amazon EBS maximum volume size of 1 TB. The log bucket is specified as part of the Create Job request. You can create an Amazon S3 bucket in the Amazon S3 section of the AWS Management Console.

Q. What happens if my storage device is larger than 1 TB?

If your storage device’s capacity is less than or equal to the maximum volume size of 1TB, its contents will be loaded directly into an Amazon EBS snapshot.

If your storage device’s capacity exceeds 1TB, a device image will be stored within your specified Amazon S3 log bucket. You can then create a RAID of EBS volumes using software such as Logical Volume Manager, and copy the image from Amazon S3 to this new volume.

Download the import/export tool

Q. Are there file system limitations when importing to Amazon EBS?

No. AWS does not mount the file system on your storage device, nor is a file system required to be present. AWS Import/Export performs a block for block copy from your device to an Amazon EBS Snapshot.


Q. How do I load my data into Amazon Glacier?

To import data to Amazon Glacier, start by loading your data onto a storage device, such as an external USB or eSATA hard drive. Then submit a Create Job request, which includes your target Amazon Glacier region and return shipping address. You’ll receive back shipping instructions in a PDF.

Print out the PDF, and cut off the barcode at the bottom of the sheet. Tape the barcode to your device, and package it along with any necessary cables. Then ship the package to the address specified in the shipping instructions.

After we load your data to Amazon Glacier, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request. PO Boxes are not a valid return shipping address. For more information about the Create Job process, please refer to the AWS Import/Export Developer Guide.

Q. What happens to my device after the import job is completed?

After we import data from your device, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request.

Q. Do I need an Amazon S3 bucket to load data into Amazon Glacier?

AWS Import/Export requires that you specify an Amazon S3 bucket that your account has write permission on for storing data loading logs. The log bucket is specified as part of the Create Job request. You can create an Amazon S3 bucket in the Amazon S3 section of the AWS Management Console.

Q. What happens if my storage device is larger than 4 TB?

If your storage device’s capacity is less than or equal to the maximum volume size of 4TB, its contents will be loaded directly into an Amazon Glacier archive.

If your storage device’s capacity exceeds 4TB, we will not load the data; we’ll erase the data on the device and send it to the Return Address specified in your Create Job request.

Download the import/export tool

Q. Are there file system limitations when importing to Amazon Glacier?

No. AWS does not mount the file system on your storage device, nor is a file system required to be present. AWS Import/Export performs a block for block copy from your device to an Amazon Glacier archive.


Q. How do I load my data into Amazon S3?

To use import, start by loading your data onto a storage device, such as an external USB or eSATA hard drive. Then submit a Create Job request, which includes your Amazon S3 bucket and return shipping address. You’ll receive back a unique JOBID, a signature for authenticating your device, and an AWS address to ship your device to.

Next, copy the signature returned from the Create Job request to the root directory of your storage device. This file must be named “SIGNATURE”. Then label your device with the JOBID and fill out the information on the packing slip. Pack your device, clearly label the JOBID on your package, and ship it to the AWS address specified in the Create Job response.

After we load your data to Amazon S3, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request. PO Boxes are not a valid return shipping address. For more information about the Create Job process, please refer to the AWS Import/Export Developer Guide.

Q. What happens to my device after the import job is completed?

After we import data from your device, we finalize the job by erasing all data on the device. (All customers creating import jobs must select the device wipe option.) We then send your device to the Return Address specified in your Create Job request.

Q. Can my data be loaded into more than one bucket?

No, data loads are restricted to one bucket per job.

Q. How are my files mapped to Amazon S3 objects?

Each filename on your storage device is mapped to an Amazon S3 key name based on its full path. For example if your storage device has a file located at “mydir/myfile”, the key will be name “mydir/myfile”. A forward slash ‘/’ is always used as the directory separator when mapping your filename to a key name. The Create Job request can include instructions for adding a prefix to each key and setting the following object attributes: Cache-Control, Content-Disposition, Content-Encoding, Content-Language, Content-Type, Expires, and x-amz-acl.

Q. Can I preserve my file metadata like permissions and timestamps?

You can preserve only a file's Last Modified Timestamp by using a Custom S3 Manifest and setting the diskTimestampMetadataKey option. File permissions are not transferred to S3 because they are not compatible with Object ACLs. For more information on setting ACLs see the Manifest file reference.

Q. What happens if a key already exists?

Just like a standard Amazon S3 PUT, if a new object uses the same key as an existing object, the AWS Import/Export overwrites the old object with the new object.

Q. Can I write to someone else’s bucket? And who pays for it?

Yes, as long as your AWS account has write access to the bucket. The AWS account that submits the Create Job request will pay all AWS Import/Export charges, while the bucket owner will pay the applicable Amazon S3 request and storage fees.

Q. Can my job span multiple disk partitions?

No, each job has exactly one partition.

Q. Can I write to a requestor pays bucket?

No, requestor pays buckets are not supported at this time. You’ll need to load your data to a non-requestor pays bucket and then either make that bucket a requestor pays bucket or copy the data to the requestor pays bucket.

Q. Do I get a checksum or any kind of receipt on what was loaded into Amazon S3?

Yes, AWS Import/Export saves an import log report to your bucket. This report contains per file information including the date and time of the upload, Amazon S3 key, MD5 checksum, and number of bytes.

Q. What happens when a file is larger than 5TB?

AWS Import/Export rejects all files larger than 5TB. We will provide the names of those files in the import log report.

Q. Can I undo a job?

No, there is no option to restore your bucket to its previous state. If you want to delete the loaded data, you’ll need to write a program to traverse your import log and issue a DELETE operation on each object.

Q. How does AWS Import/Export work with Amazon S3’s Versioning capability?

When importing your data via AWS Import/Export into a Versioning-enabled bucket, the objects within your bucket will not be permanently overwritten. The import process creates a new version for each object in your bucket. When exporting your data via AWS Import/Export from a Versioning-enabled bucket, you can only export the most recently written versions of your objects.


Q. How do I get my data from AWS?

To use export, start by sending a Create Job request to AWS which includes your Amazon S3 bucket, your encryption password and return shipping address. You’ll receive back a unique JOBID, a signature for authenticating your device, and an AWS address to ship your device to.

Next, copy the signature returned from the Create Job request to the root directory of your storage device. This file must be named “SIGNATURE”. Then label your device with the JOBID and fill out a packing slip. Pack your device, clearly label the JOBID on your package, and ship it to the AWS address specified in the Create Job response.

AWS will encrypt your data using the password you specified and transfer it onto the device. After AWS finishes transferring the data to your storage device, the device is sent to the Return Address specified in your Create Job request. PO Boxes are not a valid return shipping address. For more information about the Create job process, please refer to the  AWS Import/Export Developer Guide.

Q. Will AWS encrypt my data before loading it onto the device? Is encryption mandatory?

Yes, AWS will encrypt your data using the password you specified and transfer it onto the device. Encryption is mandatory.

Q. How much data can I fit onto my device?

It depends. The amount of data that will fit on your device is determined by the specific exported file set, your formatted device block size, the amount of file system overhead, and actual formatted capacity. For example, a 1TB drive with a raw capacity of 1,000,000,000,000 bytes, when formatted, could be left with only 910,000,000,000 usable bytes.

Block size could be an issue for file sets with smaller files. For example, if your device is formatted with 4KB block sizes, but your files are all 1KB, you would have 3KB of unusable space per file. To estimate how many bytes block size could potentially impact, multiply the number of files for export by your formatted block size.

Q. Can I retrieve data from more than one bucket?

Yes, you can specify more than one bucket in your Create Job request; however, all buckets must be located within the same Amazon S3 Region. In addition, you must have read permissions on each bucket and each object.

Q. Can I read from someone else’s bucket? And who pays for it?

Yes, as long as your AWS account has read access to the bucket and corresponding objects. The AWS account that submits the Create Job request will pay all AWS Import/Export charges, while the bucket owner will pay the applicable Amazon S3 request fees.

Q. How are my Amazon S3 objects mapped to files?

Each key is copied to your device in a directory tree that starts with the bucket’s name. For example, if the key was “images/chewie.jpg” and the bucket was “starwars”, then the object would be saved to /starwars/images/chewie.jpg. Meta data associated with each object is not copied to your storage device.

Q. What about my user metadata, ACLs, or headers?

At this time export does not include this data.

Q. Do I get a checksum or any kind of receipt on what was copied to my storage device?

Yes, AWS saves an export log report to your specified log bucket. The report contains per file information which includes the date and time of the transfer, location on your storage device, MD5 checksum, and number of bytes.

Q. What happens if a key name doesn’t map to a valid filename?

Your file will be written to the recovery directory. Your log file will contain a redirect status code.

Q. Can I specify the name of the recovery directory?

Yes, you can specify the name of the recovery directory when submitting your Create Job request. The default name is “EXPORT-RECOVERY”.

Q. Will AWS format or erase my device before starting the export?

Yes, before the export operation begins, your device will be repartitioned and re-formatted with the file system specified in your job manifest.

Q. What happens if a file already exists on my device?

The existing file will be overwritten with the new file. However before performing the export, AWS checks all keys for case sensitive name collisions on case insensitive file systems and saves duplicates to the recovery directory. For example, on FAT32 “gumby.txt” and “GUMBY.TXT” refer to the same file.

Q. Can I export data that is stored in Glacier storage class?

No, AWS Import/Export does not support exporting data that is in Glacier storage class. You will need to restore these objects in order to export them.

Q. What happens if my device is full?

An error will be flagged in your export log for each attempted key. Those objects will not be written to your storage device. You’ll need to download those files over the network or create a new job.


Q. What are the storage devices requirements?

AWS Import/Export supports storage devices that can be mounted on Red Hat Linux. For the current list of device requirements and recommended devices, please see “Selecting Your Storage Device” on the AWS Import/Export detail page.

Q. Do I need to include my USB/eSATA cable, power cable, and power supply?

Yes, for devices other than internal SATA hard drives, your package must include your connector cables, power cables and power supply. For internal SATA hard drives, no cables are necessary.

Q. How do I determine if my power supply supports 120Volts at 60Hz or 230Volts at 50 Hz?

If you have concerns, the power supply typically will have a label that specifies voltage and frequency. For example, your power supply might specify, Input: 100-240V~ 50-60Hz. This label indicates that the power supply supports voltages from 100 to 240 volts at frequencies between 50 and 60Hz. If you have additional questions, please contact your device manufacturer.


Q. What is AWS’s data security policy regarding return of devices after Import/Export jobs?

AWS only ships devices out of AWS facilities if the device is completely erased or the device only contains data encrypted by AWS. For import jobs, we erase devices after job completion. For export jobs, we will always encrypt the data being exported onto the device. We use TrueCrypt software for encryption.

Q. How is my device authenticated?

For data loads to and from Amazon S3, the Create Job response includes a unique signature, which must be copied to a file named “SIGNATURE” in the root directory of your device. For data loads into Amazon EBS and Amazon Glacier, the Create Job response includes a signature barcode, which must be taped to your device.

The signature is securely generated by AWS and is used to identify and authenticate your device. Do not share this signature with unauthorized personnel. If your signature becomes compromised, AWS recommends that you cancel the job and create a new one.

Q. Which access control mechanisms are available for AWS Import/Export?

AWS Import/Export supports Identity and Access Management (IAM) policies. With IAM policies, you can grant IAM users fine-grained control to create, view, and update Import/Export jobs.

In addition to IAM policies, you can also use bucket policies and Access Control Lists (ACLs) to limit access to your AWS resources.

Please refer to our documentation for details on using IAM policies with AWS Import/Export and granting access to related AWS resources.

Q. Where does the data load occur?

Your data will be loaded over our internal high-speed network at one of our data centers.

Q. Can I use a courier service?

You can use a courier service to send packages to AWS. For imports into and exports from US Standard, US West (Oregon) and US West (Northern California) Region buckets, AWS will return US-bound packages via UPS and international-bound packages via DHL Express Worldwide. For imports into and exports from EU (Ireland) Region buckets, AWS will return all packages via An Post. For additional information regarding return shipping fees and services, please refer to the AWS Import/Export Calculator.

Q. Will AWS wipe my device?

When you create an import job, you must specify that AWS will wipe your device. After the data load into AWS is completed all writable blocks on your storage device will be overwritten with zeroes. You will need to repartition and format your device after the wipe.

Q. Are there other situations where my data will be wiped?

The data on your device will also be wiped in situations where the Import/Export job cannot be performed. The most common reasons for this are: job cancellation by customer, unsupported file system, the device being sent to the wrong AWS facility, the device not suitable for the job to be performed, and the device missing the SIGNATURE file required to perform the job .You will not be charged for the time required to wipe your device.

Q. Who handles my package and device?

AWS uses Amazon employees and 3rd party contractors to securely process and transport your package. For example, packages shipped to our specified AWS addresses are transported to our data centers by 3rd party contractors. Your device is unpackaged only inside an AWS datacenter and handled by AWS employees who have gone through extensive background checks.

Q. Does AWS maintain a chain of custody for my package?

Yes, once a shipment arrives at the specified AWS address, AWS maintains a chain of custody for your package up until the package is delivered to your return address.

Q. What happens if my device is lost or damaged in transit?

If your device is lost or damaged in transit, you’ll need to follow up with the shipping carrier.

Q. What happens if AWS loses or damages my device?

Although AWS has a number of internal controls and procedures to prevent loss, damage or disclosure of your data, AWS is not responsible for damages associated with loss or inadvertent disclosure of data, or the loss, damage or destruction of your storage device. You should always retain a back-up copy of your data.

Q. Do I need to encrypt my data while sending a device for import?

There is no requirement to encrypt your data for import jobs. However, AWS strongly recommends encrypting any sensitive data sent to AWS on your storage device. You should determine whether your use case warrants encryption. Please refer to our documentation to learn how you can use encryption for imports.

Q. Will AWS encrypt my exported data?

Yes, all exported data will be encrypted using Truecrypt software. AWS requires that you specify an encryption password in your job creation request. You will use the same password to decrypt your exported data. See here for more information.

Q. Can AWS Import/Export destroy my device?

AWS does not provide an option for customers to request destruction of their device. However, in cases where we have to erase the data on the device and are unable to do so, our support teams will contact you at the email address specified in the Manifest file regarding device destruction.