AWS Snowmobile moves exabytes of data to the cloud in weeks by using a ruggedized, shipping-container-scale transfer truck that ships your data to an AWS region for high-speed ingest. This long-term transfer solution is designed for mission-critical migrations where network bandwidth is insufficient or time is constrained.
Organizations that need to migrate massive datasets rapidly can rely on the snowmobile data transfer service to bypass slow and costly internet egress while maintaining strict security and chain-of-custody controls throughout the move.
| Metric | Value | Unit | Notes |
|---|---|---|---|
| Typical Capacity | 100 | PB | Per snowmobile shipment |
| Max Capacity | 1000 | PB | Per snowmobile in a single load |
| Transfer Duration | 1 | Week | Typical door-to-cloud ingest timeline |
| Data Encryption | AES-256 | - | Encryption-at-rest during transport and in AWS |
| Security Model | Chain of Custody | - | GPS, video monitoring, and trained operators |
How AWS Snowmobile Works at Scale
AWS Snowmobile is an exabyte-scale data transfer service that uses a specialized truck to transport customer data directly to AWS region locations. Each vehicle can carry up to 100 petabytes on a typical run and up to 1 exabyte with optimized configurations, enabling rapid migration of datasets that would be impractical over the public internet.
The process begins with pre-provisioned storage appliances at your site, which are then loaded onto the snowmobile under secure supervision. The vehicle transports the appliances to an AWS receiving facility where the data is ingested into your AWS accounts, with end-to-end encryption and detailed audit trails ensuring security and compliance.
Planning Migration Capacity and Timeline
Capacity planning for a snowmobile move involves estimating the total dataset size, accounting for growth, and understanding the acceptable migration window. AWS recommends detailed discovery exercises to identify source systems, network constraints, and dependencies before deciding whether a single snowmobile or multiple units are required.
The timeline from hardware staging to final data availability in the cloud can be completed in weeks, depending on logistics, data volume, and regional receiving capabilities. Proper planning reduces risks associated with downtime and ensures that application cutover can proceed smoothly after the ingest completes.
Data Security and Chain of Custody Controls
Security is foundational to the AWS Snowmobile model, with AES-256 encryption applied to data at rest on the appliances and during transit inside the snowmobile. AWS maintains a strict chain of custody using GPS tracking, video surveillance, and trained security personnel to monitor each appliance from pickup through ingest.
Customers retain control of encryption keys and can integrate with existing identity and access management policies in AWS. This approach ensures that only authorized personnel and systems can access the data throughout the move, meeting stringent regulatory and compliance requirements.
Cost Considerations and Pricing Model
Pricing for AWS Snowmobile is based primarily on the volume of data transferred, logistics, and the level of service required, such as on-site setup, transport, and dedicated support. Organizations should factor in potential savings from avoided long-term bandwidth costs and reduced on-premises storage expansion when evaluating total cost of ownership.
Requests for a quote should include details about data sources, target regions, and any special handling needs, allowing AWS to design a cost-effective migration plan that aligns with business timelines and risk tolerances.
Operational Workflow and Best Practices
A successful snowmobile migration follows a clearly defined workflow that includes assessment, staging, transport, ingest, and validation phases. Coordination between infrastructure, security, and application teams ensures that dependencies are managed, cutover plans are executable, and post-move verification is thorough.
Best practices include running non-production dry runs, validating data integrity with checksums, and establishing clear communication channels with the AWS migration team. Leveraging automation for data preparation and monitoring helps reduce manual effort and improves overall reliability.
Final Recommendations for Exabyte-Scale Cloud Migration
- Perform a thorough data discovery and classification exercise before engaging AWS Snowmobile.
- Define clear success metrics, including data integrity checks and application cutover criteria.
- Coordinate closely with AWS technical account managers to align logistics and regional receiving capacity.
- Use automation for data preparation, checksum generation, and validation to reduce manual errors.
- Document the chain-of-custody process and maintain audit records for compliance and governance.
FAQ
Reader questions
How many exabytes can one AWS Snowmobile transfer in a single shipment?
One AWS Snowmobile can move up to 1 exabyte of data in a single shipment, with typical configurations handling around 100 petabytes depending on logistics and appliance density.
What level of encryption is used for data on the snowmobile?
Data is protected with AES-256 encryption at rest on the appliances and during transport, ensuring that sensitive information remains secure throughout the journey.
How long does it usually take to complete a snowmobile data transfer to AWS?
The end-to-end process, including staging, transport, and ingest, typically completes within weeks, allowing organizations to meet aggressive migration timelines.
Can AWS Snowmobile integrate with existing key management systems?
Yes, AWS Snowmobile supports integration with customer-managed keys and existing key management systems, giving organizations full control over encryption and access policies.