Using AWS Import/Export

Loading Data Using AWS Import/Export

The following figure and table describe the process AWS Import/Export uses to load your data. The sections in this part of the guide follow the process described in this figure.

Job Process

1	You copy your data to your storage device. Make sure the file paths correspond to the key names you want to use in Amazon S3. For example, if you want your Amazon S3 key to start with `images`/, place your files in a directory called `images`.
2	You create a manifest file that specifies such things as the bucket name, key prefix, and Content-Type. For more information, see Creating Manifest and Signature Files.
3	You create a new `SIGNATURE` file for your storage device by signing your manifest file from step 2 and the job ID from step 3. For more information, see Creating Manifest and Signature Files.
4	You create a new AWS Import/Export job by sending an e-mail to awsimportexport@amazon.com with the manifest file attached and “CREATE JOB” in the Subject line. The AWS Import/Export validates the manifest and returns a success e-mail with “RE: CREATE JOB” in the Subject line within one business day. The success e-mail also includes the job ID.
5	You copy the `SIGNATURE` file from step 4 to the root directory of your storage device. You must name the `SIGNATURE` file `SIGNATURE`. If you change your manifest file in any way after sending the CREATE JOB e-mail and before sending your storage device to AWS, you must send a new CREATE JOB e-mail and attach the revised manifest file.
6	You fill out the AWS Import/Export packing slip. We accept only one device per package and only one job per device.
7	You ship your storage device and packing slip to AWS. Make sure to include your job ID on the shipping label. Otherwise, we will refuse delivery of the package at the import/export facility.
8	AWS Import/Export validates the signature generated from the manifest file attached to the original CREATE JOB e-mail with the signature on the root drive of your storage device. If the signatures don’t match, the manifests differ and AWS won’t load your data. We load your data typically by the end of the next business day after we receive your storage device at the import/export facility. The timeline for loading your data depends on a number of factors, including the availability of an import station, the amount of data to load, and the data transfer rate of your device.
9	We e-mail you the status of the load and the location on Amazon S3 of the AWS Import/Export log. The log contains details about your data files that we loaded, including the key names, number of bytes, and MD5 checksum values.
10	We repack your storage device and ship it via standard ground mail to the return shipping address listed in your manifest file. This typically happens within two business days after your job completes. We do not ship to post office boxes; you must specify a street address.

How to Create a Job

This section explains how to create a job using CREATE JOB.

	Note
	This section assumes that you have already created a manifest file and a corresponding SIGNATURE file. If you have not, see Creating Manifest and Signature Files.

To create a Job

Use S3 Fox Organizer, Bucket Explorer, or a text editor to create a manifest file.
For more information, see Creating Manifest and Signature Files.
This procedure uses Manifest.txt for the name of the manifest file. You can use any name for the file.
Open your e-mail client and create a new e-mail.
Enter awsimportexport@amazon.com in the TO field and CREATE JOB in the Subject field.
Attach the Manifest.txt file to the e-mail so the e-mail looks similar to the following.
Click Send.

Within one business day you should receive an e-mail from awsimportexport@amazon.com entitled RE: CREATE JOB. See the following example e-mail below.

	Note
	Use e-mail to issue all commands. We process these requests manually each business day. If you do not get a response within one business day, please send another e-mail or contact your AWS representative.

Shipping Your Storage Device

Topics

The following sections explain how to ship your storage device to AWS. The tasks in the following procedure are explained in the sections below the procedure.

Review the following procedure before you ship your storage device to AWS.

Storage Device Packing Preparation

1	Make sure your storage device conforms to AWS requirements.
2	Create a `SIGNATURE` file.
3	Copy the `SIGNATURE` file to the root directory of your storage device.
4	Pack your storage device.
5	Create a packing slip.

Storage Device Requirements

To load your data, you must ship your storage device to AWS. To connect with our import station, your storage device must conform to specific criteria. For more information about the criteria, see Storage Device Requirements.

If your storage device cannot meet AWS requirements, contact us at awsimportexport@amazon.com.

SIGNATURE File

Your storage device must have on its root directory a file named SIGNATURE. For more information about creating that file, see Creating Manifest and Signature Files.

How to Fill Out the Packing Slip

You must fill out the AWS Import/Export packing slip so we can process your job at the import/export facility. For more information about the import/export facility, see Import Export Facility.

To fill in your packing slip

Go to http://s3.amazonaws.com/awsimportexport/AWS_Import_Export_Packing_Slip.pdf and download AWS_Import_Export_Packing_Slip.pdf.
Unzip the file and open the packing slip document.
Fill in the date, your AWS account e-mail, a contact name, a contact phone number or e-mail, and a storage device ID.
Each package can contain only one storage device and each storage device can have only one device ID, such as a serial number.

The following is an example packing slip.

How to Pack Your Storage Device

This section describes how to pack your media and packing slip so you can ship it to the import/export facility. For more information about the packing slip, see How to Fill Out the Packing Slip.

To pack your storage device

Make sure that you package your equipment appropriately. Your shipper can provide packing guidelines. For more information, go to:

UPS—http://www.ups.com/content/us/en/resources/prepare/guidelines/prepare_package1.html

FEDEX—http://fedex.com/ca_english/shippingguide/preparepackage

	Important
	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 the physical hardware. You should always retain a back-up copy of your data.

Enclose your device and your device’s power supply, power cable, and data connector.
Enclose your filled-out packing slip

How to Ship Your Storage Device

This section describes how to fill out the shipping label and send the package to AWS. For more information about packing your storage device, see How to Pack Your Storage Device.

To fill out your shipping label and send your storage device

Fill out the shipping label by writing on it the import/export facility’s mailing address and the unique job ID. For example, if your job ID is 48973, your shipping label would be:

AWS Import/Export
JOBID 48973
2646 Rainier Ave South Suite 1060
Seattle, WA 98144

	Important
	The shipping label must include a valid job ID. If that information is missing, AWS will refuse delivery of your storage device and your carrier will process it as an undelivered package. For more information about the job ID, see Job.

Fill in your return shipping address.

Include a contact phone number in case we have a problem processing your storage device.

	Important
	If AWS Import/Export refuses the delivery of your package, the carrier uses the return shipping address to return your storage device. After AWS processes your job, however, we return your storage device to the return address you specified in your manifest file, not the return address listed on your shipping label.

Ship your package using the carrier of your choice.

Send Us Your Feedback Now

Your input is important to us to help make our documentation helpful and easy to use. Please take a minute to give us your feedback on how well we were able to ship your storage device. Just click this Feedback link. Thank you.

Requesting Status

After shipping your storage device, you can check on the status of your job. To do that, you use the GET STATUS command.

There are two different status codes that the system tracks: your device status and your job status. The typical device status flow is:

NotReceived
AtAWS
Returned

The typical job status flow is:

Pending
InProgress
Completed

For more information about status, see GET STATUS.

To request status

Open your e-mail client and create a new e-mail.
Important
You must send the e-mail from the same AWS account you used to send the CREATE JOB e-mail.
Enter awsimportexport@amazon.com into the TO field, GET STATUS in the Subject field, and JOBID: [job ID] in the body.
Click Send.

After approximately one business day you should receive an e-mail from awsimportexport@amazon.com with the subject RE: GET STATUS.

For more details about device and job status codes, see Status Codes and Descriptions.

How to Update Your Job

If you need to update your job after you've shipped your storage device and before we have processed it, you can either cancel the job or update it. If you cancel the job, we return your storage device and then you submit a revised JOB CREATE request. For more information, see How to Cancel Your Job and How to Create a Job.

If you want to update your job request, you send us an UPDATE JOB e-mail to which you attach an updated SIGNATURE file and manifest file. When we receive your package, we confirm that the SIGNATURE file on your storage device authenticates with the manifest file sent with the CREATE JOB request. After that confirmation, we use the updated manifest file attached to the UPDATE JOB e-mail to load your data.

Use the following process to update your job.

Updating Your Job

1	Send a `GET STATUS` request. The status of your job must be `Pending`. If the status is `InProgress` or `Completed`, it is too late to send an `UPDATE JOB` request.
2	Revise your manifest file with your updated values. For more information, see Manifest File.
3	Revise your `SIGNATURE` file. For more information, see Creating a Signature File.
4	Send an `UPDATE JOB` request. For more information, see UPDATE JOB.

How to Cancel Your Job

There might be a time when you no longer need to load the data that you shipped on your storage device to Amazon S3. In this case, you should cancel the job. When you cancel a job, we return your storage device and send you an e-mail to confirm the cancellation.

Important

You are charged for device and data transfer fees once we begin the data load. There typically is a delay between your CANCEL JOB e-mail and when we cancel the job. You are responsible for all device and transfer fees for the data loaded before we cancel the job. There are no refunds of transfer fees for data we have loaded.

You cannot cancel a completed job.

To cancel a job

Send a GET STATUS request.
The status of your job must be Pending or InProgress. If the status is Completed, it is too late to send a CANCEL JOB request.
Send a CANCEL JOB request.
For more information, see CANCEL JOB.

How to View Log Files

For each successful job, AWS Import/Export generates a log file. The log file is a UTF8 encoded CSV file that contains, among other things, information about each file loaded from your storage device.

AWS Import/Export saves the log files to the same Amazon S3 bucket as your data. The log file name always ends with the phrase import-log- followed by your JOBID. For example, if the JOBID is 53TX4, the log file name would end in import-log-53TX4. By default, if you do not set logPrefix in the manifest file, a job loaded to mybucket with the JOBID of 53TX4 loads the logs tohttp://mybucket.s3.amazonaws.com/import-log-53TX4. If you set logPrefix to logs/, the log file location would be http://s3.amazonaws.com/mybucket/logs/import-log-53TX4.

	Note
	If you have a log file name with the same name as an existing Amazon S3 object, the new log file overwrites the existing object. You can use the `logPrefix` field to prevent object collisions. For more information about `logPrefix`, see Manifest File.

To view the log files

You can use S3curl or S3 Foxfire Organizer.
For more information, see Amazon S3 Bucket Creation.

Sample Log File

The following shows a sample log file.

DateTime	File	Status	Code	Key	MD5	Bytes	Content-Type
Tue 03 Feb 200921:57:43 GMT	"SIGNATURE"	103	Ignore			90	application/octet-stream
Tue 03 Feb 200921:57:43 GMT	"Notice.txt"	200	OK	"toady/images/Notice.txt"	f60fe317bc497b1204b327094959eb64	13	text/plain
Tue 03 Feb 200921:57:43 GMT	"README.txt"	200	OK"	toady/images/README.txt"	d5a46fa22596d2464eff10babb19000e	13	text/plain
Tue 03 Feb 200921:57:43 GMT	"images/wookie1.jpg"	200	OK	"toady/images/images-wookie1.jpg"	ccac0d031603ff1c2994e07703a64845	497	image/jpeg
Tue 03 Feb 200921:57:43 GMT	"images/chewie.GIF"	200	OK	"toady/images/images-chewie.GIF"	5fc22dc594e0c5929c090b9585ba9e70	878	image/gif
Tue 03 Feb 200921:57:43 GMT	"images/resources/chewie.psd"	200	OK	"toady/images/images-resources-chewie.psd"	130b64d171e9bbc2a8dbe117f189796c	524	application/octet-stream
Tue 03 Feb 200921:57:43 GMT	"images/chewie.TIF"	200	OK	"toady/images/images-chewie.TIF"	823d17b05321b96e01f9174e3dcace7	458	image/tiff

Log File Fields

The following table describes the fields in the log file.

Field Description

DateTime The date and time when we processed a file, for example, Wed Nov 12 11:07:34 PST 2008.

File

The name of the file in the root directory of your storage device, for example, "/images/image.jpg".

	Note
	All `File` and `Key` values are surrounded by quotes.

Status Specifies either an AWS Import/Export status or one of the standard Amazon S3 REST web server HTTP status codes, for example, 200. For more information, see AWS Import/Export Status Codes.

Code Specifies either an AWS Import/Export code, such as Ignored when the Status is 103, or the standard Amazon S3 REST error codes, for example, OK.

Key

Specifies where AWS Import/Export loads the file in Amazon S3. The key includes the bucket name and any prefix settings set in the manifest file, for example, "/mybucket/myprefix/images/image.jpg".

	Note
	All `File` and `Key` values are enclosed in quotes.

MD5 The checksum of the object stored in Amazon S3 identified by Key, for example, d2a22fcab097sample32c544.

Bytes The number of bytes stored in S3 for the object identified by Key, for example, 57344.

Content-Type The content type of the key stored in Amazon S3, for example, image/jpeg.

Status

For a list of status values you might find in the log files, see Status Codes.

	Important
	You must send the e-mail from the same AWS account you used to send the `CREATE JOB` e-mail.