/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Amazon debuts AWS Snowmobile, a 45 foot long container and truck capable of transporting 100PB of data securely between locations

Moving large amounts of on-premises data to the cloud as part of a migration effort is still more challenging than it should be!

AWS Blog Jeff Barr

Context & Ripple Effects

The Snowmobile is the extreme end of a migration push AWS began earlier: in 2015 it rolled out a faster data-transfer method aimed at non-technical users, and the truck extends that logic to customers whose archives are too large for network upload. A 45-foot container carrying 100PB per trip turns exabyte-scale migration into a logistics problem AWS can price and schedule.

The launch also seeds a device line, not just a vehicle: by 2018 AWS put a local version of EC2 inside Snowball Edge, showing the same physical-transfer family expanding toward edge compute. The later arc matters for judging the bet — AWS eventually discontinued Snowmobile in 2024 and replaced the model with Data Transfer Terminal, fixed locations where customers plug in their own storage devices.

First-order effects

  • Enterprises with petabyte-to-exabyte on-premises archives gain a viable path to AWS that bypasses network transfer time entirely, making multi-year migration timelines compressible into truck shipments.
  • AWS's migration sales pitch changes immediately: the hardest objection in large enterprise deals — 'our data is too big to move' — now has a first-party answer, pressuring Microsoft and Google to match on their own large-migration offerings.

Second-order effects

  • The Snowball/Snowmobile hardware family becomes a platform: once AWS controls the physical ingress path, adjacent services like the cheaper Glacier archive tier launched for 2019 become the natural landing zones for trucked data, deepening lock-in at the storage layer.
  • Data-intensive S3 workloads later get their own acceleration track — the 10x-write S3 Express One Zone tier — indicating AWS is optimizing both ends of the pipeline, ingress and in-cloud performance, for the customers the truck recruits.

Third-order effects

  • If the pattern holds, physical data transport evolves from bespoke heavy logistics (a dedicated 18-wheeler) toward standardized infrastructure — the 2024 shift from Snowmobile to fixed Data Transfer Terminals suggests AWS concluded scheduled trucking was too niche, and drop-off points scale better across the customer base.
  • The longer arc points to migration logistics becoming a commoditized cloud-onboarding utility: whoever operates the physical ingress network — AWS today — converts data gravity into durable multi-service lock-in across compute, storage, and analytics.

The trend: Cloud data migration is moving from one-off physical stunts toward standardized physical-ingress infrastructure, with AWS iterating from the Snowmobile truck to fixed transfer terminals as it chases enterprise archives.