What to do if AWS Storage Snowball becomes locked during data transfer?
If you're transferring data to the Snowball and it becomes locked, return the appliance and start a new job to transfer the remaining data. If it locks during an import job, the existing data on the Snowball can still be transferred into Amazon S3.
Why does AWS Storage Snowball client cause Java OutOfMemoryError?
If the Java OutOfMemoryError exception appears while running the Snowball client, it means your workstation is running out of memory. To resolve this, free up resources or increase the memory allocated to your workstation, and then try running the Snowball client task again.
How to get help with AWS Storage Snowball client?
If you're having trouble using the Snowball client, type the command snowball help. This will display a list of all available actions for the tool.
What to do if AWS Storage Snowball data transfer has unexpected errors?
If you're encountering unexpected errors during data transfer to the Snowball, create a copy of your logs and include them with a brief description of the issues you encountered. Then send this information to AWS Support.
How to fix AWS Snowball Storage error: key's length is larger than 933 bytes?
To resolve the error message about a key's length being larger than 933 bytes, reduce the object's key length.
What to do if AWS Snowball files failed export to Windows Server?
If files failed export to a Microsoft Windows Server, it means that a file or a related folder is named in a format not supported by Windows. To fix this, change the names of the objects in Amazon S3 that are causing the issue to remove or replace the unsupported characters.
How to fix AWS Snowball import failure due to invalid characters?
If files failed import into Amazon S3 due to invalid characters in object names, it means that a file or folder name has characters that aren't supported by Amazon S3. To resolve this, create a new Snowball import job, change the file and folder names to comply with Amazon S3 rules, and transfer the files again.
Why can't I upload UTF-8 files to AWS Storage Snowball?
If you can't upload files with UTF-8 characters to a Snowball, it's because your Linux workstation doesn't recognize UTF-8 character encoding. Install the locales package on your Linux workstation and configure it to use one of the UTF-8 locales like en_US.UTF-8. You can configure the locales package by exporting the environment variable LC_ALL, for example: export LC_ALL=en_US.UTF-8.
What to do if data can't be transferred into the root folder of AWS Storage Snowball?
Make sure that you're transferring data into a folder on the Snowball that is not the root folder.
General| Encryption | 256-bit encryption |
|---|---|
| Data Transfer Method | Physical shipment |
| Security | Tamper-resistant enclosure, Trusted Platform Module (TPM) |
| Storage Capacity | 80 TB |
| Durability | Designed for rugged environments |
| Operating Environment | Indoor and outdoor environments |
| Weight | Approximately 50 lbs |
| Compatible Services | Amazon S3, Amazon EC2, Amazon EBS, AWS Lambda |
To Next Page