Jobs in AWS Snowball
A job in AWS Snowball (Snowball) is a discrete unit of work, defined when you create it in the console or the job management API. There are two different job types: import jobs and export jobs. Although these two types of jobs have fundamental differences, they share some common details.
Both of the Snowball job types are summarized following, including the source of the data, how much data can be moved, and the result you can expect at successful job completion. The source can be local to your data center or office, or it can be an Amazon S3 bucket.
Import into Amazon S3
An import job is the transfer of 80 TB or less of your data (located in an on-premises data source), copied onto a single Snowball, and then moved into Amazon S3. For import jobs, Snowballs and jobs have a one-to-one relationship, meaning that each job has exactly one Snowball associated with it. If you need additional Snowballs, you can create new import jobs or clone existing ones.
Your data source for an import job should be on-premises. In other words, the storage devices that hold the data to be transferred should be physically located at the address that you provided when you created the job.
You can import any number of directories, files, and objects for each import job, provided the amount of data your importing fits within a single Snowball. In the US regions, Snowballs come in two sizes: 50 TB and 80 TB. All other regions have 80 TB Snowballs only.
When you import files, each file becomes an object in Amazon S3 and each directory becomes a prefix. If you import data into an existing bucket, any existing objects with the same names as newly imported will be overwritten.
When the import has been processed and verified, AWS performs a complete erasure of the Snowball. This erasure follows the National Institute of Standards and Technology (NIST) 800-88 standards.
After your import is complete, you can download a job report. This report alerts you to any objects that failed the import process. You can find additional information in the success and failure logs.
Don't delete your local copies of the transferred data until you can verify the results of the job completion report and review your import logs.
Export from Amazon S3
An export job is the transfer of any amount of data (located in Amazon S3), copied onto any number of Snowballs, and then moved one Snowball at a time into your on-premises data destination. When you create an export job, it's split into job parts. Each job part is no more than 80 TB in size, and each job part has exactly one Snowball associated with it.
Your data source for an export job is one or more Amazon S3 buckets. Once the data for a job part is moved from Amazon S3 to a Snowball, you can download a job report. This report will alert you to any objects that failed the transfer to the Snowball. You can find more information in your job's success and failure logs.
You can export any number of objects for each export job, using as many Snowballs as it takes to complete the transfer. Snowballs for an export job's job parts are delivered one after another, with subsequent Snowballs shipping out to you once the previous job part has entered the In transit to AWS status.
When you copy objects into your on-premises data destination from a Snowball, those objects are saved as files. If you copy objects into a location that already holds files, any existing files with the same names will be overwritten.
When AWS receives a returned Snowball, we perform a complete erasure of the Snowball. This erasure follows the NIST 800-88 standards.
Don't change, update, or delete the exported Amazon S3 objects until you can verify that all of your contents for the entire job have been copied to your on-premises data destination.
When you create an export job, you can choose to export an entire Amazon S3 bucket or a specific range of objects keys. For more information, see Using Export Ranges.
Each import or export job for Snowball is defined by the details that you specify when it's created. The following list describes all the details of a job.
Job name – A name for the job, containing alphanumeric characters, spaces, and any Unicode special characters.
Job type – The type of job, either import or export.
Job ID – A unique 39-character label that identifies your job. The job ID appears at the bottom of the shipping label that appears on the E Ink display, and in the name of a job's manifest file.
Created date – The date that you created this job.
Shipping speed – Speed options are based on region. For more information, see Shipping Speeds.
IAM role ARN – This Amazon Resource Name (ARN) is the AWS Identity and Access Management (IAM) role that is created during job creation with write permissions for your Amazon S3 buckets. The creation process is automatic, and the IAM role that you allow Snowball to assume is only used to copy your data between your Amazon S3 buckets and the Snowball. For more information, see Creating an IAM Role for Snowball.
AWS KMS key – In Snowball, AWS Key Management Service (AWS KMS) encrypts the keys on each Snowball. When you create your job, you also choose or create an ARN for an AWS KMS encryption key that you own. For more information, see AWS Key Management Service in Snowball.
Snowball capacity – In the US regions, Snowballs come in two sizes: 50 TB and 80 TB. All other regions have the 80 TB Snowballs only.
Storage service – The AWS storage service associated with this job, in this case Amazon S3.
Resources – The AWS storage service resources associated with your job. In this case, these are the Amazon S3 buckets that your data is transferred to or from.