/
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
Handles
Browse by social media handle
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

How Amazon Followed Google Into the World of Secret Servers

Chris Pinkham was walking through a data center that would one day house Amazon's seminal cloud computing service — the Elastic Compute Cloud — when he came face to face with a cage of Google machines.

Wired Cade Metz

Context & Ripple Effects

By late 2012 the story of how cloud computing began had settled into a familiar arc: Google spent years building its own servers behind closed doors, a practice that cost traditional hardware vendors dearly when it surfaced in EE Times' 2008 reporting on server makers getting 'Goooogled', and Google even showed off some of that design in Rough Type's 2009 'lifts its skirts' piece. What was less understood until this Wired account is that Amazon's Elastic Compute Cloud grew out of the same instinct — Chris Pinkham literally walked past a cage of Google machines in the data center destined for EC2.

The piece matters because it reframes EC2 not as an invention from nowhere but as Amazon copying Google's operational playbook and then doing something Google did not: selling that hidden infrastructure to outsiders. The syndication trail — picked up by handles including Sequoia Capital's — shows how much appetite there was for origin stories of the cloud just as AWS was becoming the industry's reference point.

First-order effects

  • Amazon's decision to rent out what Google kept internal turned a secrecy-driven cost advantage into a revenue line, making raw compute a purchasable commodity rather than a proprietary edge.

Second-order effects

  • Rivals running large private fleets faced pressure to either open their infrastructure as services or watch Amazon monetize scale they could not; meanwhile the hardware-bypass pattern documented in the 2008 server-maker coverage spread, as whoever operated at cloud scale designed its own machines.

Third-order effects

The trend: Web-scale companies are converting internally engineered, closely held data-center infrastructure into rentable cloud platforms, with Amazon's EC2 as the template Google chose not to follow.