| « PreviousNext » | |
   | Did this page help you? Yes | No | Tell us about it... |
AWS Import/Export Concepts
This section describes key concepts and terminology you need to understand to use AWS Import/Export effectively.
Job
Creating an AWS Import/Export job is a two-step process. First, you submit a job request to AWS. Each AWS Import/Export job corresponds to exactly one storage device. You submit your job request by using the AWS Import/Export command line tool, which requires no programming. If your application requires a programmatic interface, you can use the AWS SDK or the REST API.
You must submit a separate job request for each device.
Note
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.
When you send your storage device to AWS, we use our high bandwidth network to import your data into AWS or export data from AWS to your storage device, then return your device.
Job Type
This section summarizes the AWS Import/Export job types.
AWS Import/Export supports these job types:
Import to Amazon S3
Export from Amazon S3
Import to Amazon Glacier
Import to Amazon EBS
Import to Amazon S3
- Source—Files on a device file system. One device per import job.
- Target—Objects in an existing Amazon S3 bucket. One bucket per import job.
- Result—One object for each file. Files and directories can be excluded or renamed using manifest file options.
Export from Amazon S3
- Source—Objects in one or more Amazon S3 buckets. Multiple buckets per export job.
- Target—Files on your storage device. One device per export job.
- Result—One file for each object. You can export from more than one bucket and specify which files to export using manifest file options.
Import to Amazon Glacier
- Source—Entire device. One device per import job.
- Target—Archive in an existing Amazon Glacier vault. One archive per import job.
- Result—A device image stored as a single archive. The device's file sytem is never mounted.
Important
An import to EBS will have different results depending on whether the capacity of your storage device is 1TB or less or greater than 1 TB.
Import to Amazon EBS (up to 1 TB)
- Source—Entire device, where the device capacity is 1 TB or less. One device per import job.
- Target—Amazon EBS snapshot. One snapshot per import job.
- Result—A device image stored as a single snapshot. The device's file sytem is never mounted.
Import to Amazon EBS (more than 1 TB)
- Source—Entire device, where the device capacity is greater than 1 TB. One device per import job.
- Target—Objects in an existing Amazon S3 bucket. One device image, multiple Amazon S3 objects per import job.
- Result—A device image chunked as a series of 1 TB snapshots that are stored as objects in the Amazon S3 bucket specified in the
logBucketmanifest file option. The device's file system is never mounted.
Manifest File
When sending a create job request for an import or export operation you describe your job in a text file called manifest. For example, you describe whether the job is an import or an export job, your AWS Access Key ID, the address to return your storage device to, and an Amazon S3 bucket.
Signature File
A signature is an encrypted string that allows us to authenticate your import or
export job to Amazon S3. In response to your CreateJob request
for an import job to Amazon S3, AWS sends a SIGNATURE value in
the response and writes a SIGNATURE file to your drive. You copy this file to the
root directory of your storage device.
If the SIGNATURE file is missing or invalid,
AWS Import/Export will not perform the data load and we will return your storage
device.
Barcode
We use a barcode to authenticate your import to Amazon EBS or Amazon Glacier. In
response to your CreateJob request, AWS sends a PDF file with a
barcode to your computer to the bucket you specified for logging in the import
manifest. You print out the barcode and attach it to your device.
If the barcode is missing or invalid, AWS Import/Export will not perform the data load and we will return your storage device.
Log File
After successfully transferring data between AWS and your portable storage device, AWS Import/Export generates a log file. The log file is a CSV file that contains, among other things, information about each file loaded to or from your storage device.
Related Concepts
To learn more about Amazon S3, see Introduction to Amazon S3.
To learn more about Amazon EBS, go to Amazon Elastic Block Store.
To learn more about Amazon Glacier, go to Amazon Glacier.
