Best Practices for AWS Snowball
This checklist is intended to help you get the maximum benefit from and satisfaction with AWS Snowball (Snowball).
If you notice anything that looks suspicious about the Snowball, don't connect it to your internal network. Instead, contact AWS Support, and a new Snowball will be shipped to you.
We recommend that you don't save a copy of the unlock code in the same location in the workstation as the manifest for that job. Saving these separately helps prevent unauthorized parties from gaining access to the Snowball. For example, you can save a copy of the manifest to the workstation, and email the code to the AWS Identity and Access Management (IAM) user to perform the data transfer from the workstation. This approach limits access to the Snowball to individuals who have access to files saved on the workstation and also that IAM user's email address.
Whenever you transfer data between your on-premises data centers and a Snowball, plaintext logs are automatically generated and saved to your workstation. These logs are saved in plaintext format and can contain file name and path information for the files that you transfer. To protect this potentially sensitive information, we strongly suggest that you delete these logs once the job that the logs are associated with enters the Completed status. For more information about logs, see Snowball Logs.
Your workstation should be the local host for your data. For performance reasons, we don't recommend reading files across a network when using Snowball to transfer data. If you must transfer data across a network, batch the local cache before copying to the Snowball so the copy operation is able to proceed as fast as possible.
Because the workstation is considered to be the bottleneck for transferring data, we highly recommend that your workstation be a powerful computer, able to meet high demands in terms of processing, memory, and networking. For more information, see Workstation Specifications.
You can run simultaneous instances of the Snowball client in multiple terminals, each using the copy operation to speed up your data transfer. For more information about using the Snowball client see Commands for the Snowball Client.
To prevent corrupting your data, do not disconnect the Snowball or change its network settings while transferring data.
Files must be in a static state while being copied. Files that are modified while they are being transferred will not be imported into Amazon S3.
The 10 free days for performing your on-premises data transfer start the day after the Snowball arrives at your data center, and stop when you ship the appliance back out.
The Job created status is the only status in which you can cancel a job. When a job changes to a different status, it can’t be canceled.
For import jobs, don't delete your local copies of the transferred data until the import into Amazon Simple Storage Service (Amazon S3) is successful at the end of the process and you can verify the results of the data transfer.