AWS Snowmobile: What It Is and When to Use It

Service Update: As of early 2024, AWS has reportedly phased out the AWS Snowmobile service. Customers with exabyte-scale data transfer needs are now guided towards using multiple AWS Snowball Edge devices or online transfer services like AWS DataSync over AWS Direct Connect. This article is retained for informational and historical purposes.

Definition

AWS Snowmobile was an exabyte-scale data transfer service designed to move extremely large datasets, up to 100 petabytes (PB) per vehicle, from on-premises data centers to the AWS cloud. It consisted of a 45-foot long, ruggedized shipping container pulled by a semi-trailer truck, effectively acting as a data center on wheels to solve the challenge of migrating massive volumes of data that would be impractical to transfer over the internet.

How It Works

The process for using AWS Snowmobile was a fully managed, high-touch engagement with AWS, involving several key phases:

1. Initial Consultation & Site Survey: The process began with a consultation where AWS personnel would work with the customer to assess their data migration needs, network infrastructure, and physical site logistics.
2. Deployment: AWS would drive the Snowmobile to the customer's data center. The container was climate-controlled, water-resistant, and tamper-resistant, and could be parked in a covered or uncovered area.
3. Connection & Configuration: AWS personnel would handle all logistics, including connecting the Snowmobile to the local network. The truck was equipped with a high-speed switch and cabling capable of up to 1 Tbps of data transfer, spread across multiple 40 Gbps connections. Once connected, the storage inside the Snowmobile appeared as a local, Network File System (NFS) mounted volume, allowing customers to use their existing backup and transfer tools.
4. Data Transfer: The customer would then copy their data to the Snowmobile. With sufficient network bandwidth, a full 100 PB transfer could be completed in about 10 days.
5. Transport & Ingestion: After the data transfer was complete, AWS personnel would drive the Snowmobile to a designated AWS Region. The journey was secured with GPS tracking, video surveillance, and an optional security vehicle escort. Upon arrival, the data would be ingested directly into Amazon Simple Storage Service (Amazon S3) or Amazon S3 Glacier.

Key Features and Limits

• Massive Capacity: A single Snowmobile could transport up to 100 PB of data, equivalent to roughly 1,250 AWS Snowball Edge devices.
• High-Speed Transfer: The onboard networking hardware supported an aggregate transfer speed of up to 1 Tbps, making it significantly faster than internet-based transfers for exabyte-scale datasets.
• Multi-Layered Security: Security was a critical component. It included:
  • Physical Security: The container was tamper-resistant, and access was restricted to authorized AWS personnel. It featured 24/7 video surveillance, alarm monitoring, and GPS tracking. A security vehicle escort was also an option during transit.
  • Data Encryption: All data was encrypted with 256-bit encryption keys managed by the customer using the AWS Key Management Service (AWS KMS).
• Ruggedized Design: The Snowmobile was a 45-foot long, climate-controlled, and water-resistant shipping container designed to protect the hardware inside.

Common Use Cases

AWS Snowmobile was the right choice for one-time, massive data migration projects that were too large for any other method.

• Complete Data Center Migration: Moving an entire on-premises data center, with exabytes of data, to AWS.
• Video Library & Media Archive Migration: For media and entertainment companies needing to move vast repositories of high-resolution video, audio, and production archives to the cloud.
• Scientific and Research Data Relocation: Transferring massive datasets from scientific research, such as genomic sequences, satellite imagery, or financial modeling data.
• Large-Scale Disaster Recovery: Enabling the swift migration of huge backup datasets to AWS to build out a disaster recovery (DR) environment.

Pricing Model

Pricing for AWS Snowmobile was not available on a standard, pay-as-you-go basis. Instead, it was based on a custom quote following a consultation with the AWS team. The final price would depend on the amount of data to be transferred and the duration of the Snowmobile's use on-site. The service was designed to be more cost-effective and significantly faster than transferring exabytes of data over a high-speed internet connection.

Pros and Cons

Pros:

• Unmatched Scale: It was the only practical solution for moving datasets in the exabyte range in a reasonable timeframe.
• Speed: For its target use case, it was dramatically faster than any network-based transfer, turning a process that could take years or decades into a matter of weeks.
• Robust Security: Comprehensive physical and digital security measures, including encryption, GPS tracking, and dedicated security personnel, ensured a full chain-of-custody.

Cons:

• Logistical Complexity: Required significant planning, a physical site survey, and space to park a 45-foot semi-trailer truck.
• High Power Requirement: The unit consumed about 350 kW of power, which might require a dedicated generator if the data center could not provide it.
• Niche Application: Only suitable for the largest possible data migration projects (10 PB and above).
• Service Decommissioned: The service is no longer available, with customers now directed to use multiple Snowball devices or online methods.

Comparison with Alternatives

AWS Snowmobile was the largest member of the AWS Snow Family, designed for different data volumes:

• AWS Snowball Edge: These are rugged, suitcase-sized devices used for petabyte-scale data transfers (typically up to 80 TB per device for Storage Optimized models). Multiple Snowball Edge devices are now the recommended physical transfer method for migrations larger than what a single device can handle.
• AWS Snowcone: The smallest member of the family, Snowcone is a portable, rugged device for terabyte-scale data transfers (up to 8 TB for the HDD model). It's ideal for edge computing, IoT data collection, and smaller migration jobs.
• AWS Direct Connect + AWS DataSync: For ongoing large-scale data transfers, customers can establish a dedicated private network connection to AWS with Direct Connect and use DataSync to automate and accelerate the online transfer. This is now a primary alternative for large migrations where sufficient network bandwidth is available.

Exam Relevance

Even though the service is retired, AWS Snowmobile may still appear on certification exams as a point of reference for understanding the scale of different data transfer solutions. For exams like the AWS Certified Cloud Practitioner (CLF-C01) and AWS Certified Solutions Architect - Associate (SAA-C03), candidates should know:

• Its purpose: for exabyte-scale data transfer (10 PB or more).
• Its place in the Snow Family: as the largest capacity option, significantly bigger than Snowball and Snowcone.
• When to choose it: Understand that for a question involving migrating 50 PB of data, Snowmobile would have been the correct answer over using hundreds of Snowballs or relying on a network connection.

Frequently Asked Questions

Q: How much data could a single AWS Snowmobile hold?

A: A single AWS Snowmobile could transport up to 100 petabytes (PB) of data.

Q: How was data kept secure during a Snowmobile transfer?

A: AWS employed a multi-layered security strategy. This included 256-bit encryption using customer-managed keys via AWS KMS, a tamper-resistant physical container, 24/7 video surveillance, GPS tracking, alarm monitoring, and the option for a dedicated security vehicle escort during transit.

Q: How long did it take to fill a Snowmobile with data?

A: With a 1 Tbps connection, a Snowmobile could be filled with 100 PB of data in approximately 10 days, assuming the customer's on-premises network could sustain that transfer rate.

---

This article reflects AWS features and pricing as of 2026. AWS services evolve rapidly — always verify against the official AWS documentation before making production decisions.