Using the Snowball Client
Following, you can find an overview of the Snowball client, one of the tools that you can use to transfer data between your on-premises data center and the Snowball. The Snowball client supports transferring the following types of data to and from a Snowball.
Sources of data that can be imported with the Snowball client are as follows:
Files or objects hosted in locally mounted file systems.
Files or objects from a Hadoop Distributed File System (HDFS) cluster. Currently, only HDFS 2.x clusters are supported.
Each file or object that is imported must be less than or equal to 5 TB in size.
Because the computer workstation from which or to which you make the data transfer is considered to be the bottleneck for transferring data, we highly recommend that your workstation be a powerful computer. It should be able to meet high demands in terms of processing, memory, and networking. For more information, see Workstation Specifications.
Testing Your Data Transfer with the Snowball Client
You can use the Snowball client to test your data transfer before it begins. Testing is useful because it can help you identify the most efficient method of transferring your data. The first 10 days that the Snowball is onsite at your facility are free, and you'll want to test your data transfer ahead of time to prevent fees starting on the eleventh day.
You can download the Snowball client from the tools page at any time, even before you first log in to the AWS Snowball Management Console. You can also use the Snowball client to test your data transfer job before you create the job, or any time thereafter. You can test the Snowball client without having a manifest, an unlock code, or a Snowball.
To test data transfer using the Snowball client
Download and install the Snowball client from the AWS Snowball Tools Download page.
Ensure that your workstation can communicate with your data source across the local network. We recommend that you have as few hops as possible between the two.
Run the Snowball client's test command and include the path to the mounted data source in your command as follows.
snowball test [OPTION...] [path/to/data/source]
The preceding example commands tell the Snowball client to run the test recursively through
all the folders and files found under
/Logs/2015/August on the data
source for 5 minutes, and tell the Snowball client to report real-time transfer speed data for the
duration of the test.
The longer the test command runs, the more accurate the test data you get back.
Authenticating the Snowball Client to Transfer Data
Before you can transfer data with your downloaded and installed Snowball client, you must
first run the
snowball start command. This command authenticates your access
to the Snowball. For you to run this command, the Snowball you'll use for your job
must be onsite, plugged into power and network, and turned on. In addition, the E Ink
display on the Snowball's front must say Ready.
To authenticate the Snowball client's access to a Snowball
Obtain your manifest and unlock code.
Get the manifest from the AWS Snowball Management Console or the job management API. Your manifest is encrypted so that only the unlock code can decrypt it. The Snowball client compares the decrypted manifest against the information that was put in the Snowball when it was being prepared. This comparison verifies that you have the right Snowball for the data transfer job you’re about to begin.
Get the unlock code, a 29-character code that also appears when you download your manifest. We recommend that you write it down and keep it in a separate location from the manifest that you downloaded, to prevent unauthorized access to the Snowball while it’s at your facility.
Locate the IP address for the Snowball on the Snowball's E Ink display. When the Snowball is connected to your network for the first time, it automatically creates a DHCP IP address. If you want to use a different IP address, you can change it from the E Ink display. For more information, see Using the Snowball Appliance.
snowball startcommand to authenticate your access to the Snowball with the Snowball's IP address and your credentials, as follows:
snowball start -i [IP Address] -m [Path/to/manifest/file] -u [29 character unlock code]
Schemas for Snowball Client
The Snowball client uses schemas to define what kind of data is transferred between your on-premises data center and a Snowball. You declare the schemas whenever you issue a command.
Sources for the Snowball Client Commands
Transferring file data from a local mounted file system, requires that you specify
the source path as you would according to your OS type. For example, in the command
snowball ls C:\\User\Dan\CatPhotos s3://MyBucket/Photos/Cats, the source
schema specifies that the source data is standard file data.
For importing data directly from a Hadoop Distributed File System (HDFS) to a
Snowball, you specify the Namenode URI as the source schema, which has the
format. For example:
snowball cp -n hdfs://localhost:9000/ImportantPhotos/Cats s3://MyBucket/Photos/Cats
Destinations for the Snowball Client
In addition to source schemas, there are also destination schemas. Currently, the
only supported destination schema is
s3://. For example, in the command
snowball cp -r /Logs/April s3://MyBucket/Logs, the content in
/Logs/April is copied recursively to the
location on the Snowball using the
When you transfer data between your on-premises data centers and a Snowball, the Snowball client automatically generates a plaintext log and saves it to your workstation. If you encounter unexpected errors during data transfer to the Snowball, make a copy of the associated log files and include them along with a brief description of the issues that you encountered in a message to AWS Support.
Logs are saved in the following locations, based on your workstation's operating system:
Windows – C:/Users/
Mac – /Users/
Linux – /home/
Logs are saved with the file name
The hour is based on local system time for the workstation and uses a 24-hour
Example Log Name
Each log has a maximum file size of 5 MB. When a log reaches that size, a new file is
generated, and the log is continued in the new file. If additional logs start within the
same hour as the old log, then the name of the first log is appended with
and the second log is appended with
.2, and so on.
Logs are saved in plaintext format and 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.