AWS

The side project that ate the software industry — how Amazon started renting out its own plumbing and built the cloud.

The accident that wasn’t

By the early 2000s Amazon had built formidable internal infrastructure for its retail business — and, in Bezos’s telling, every team was rebuilding the same undifferentiated plumbing. Around 2003, work began on standardizing it. The famous internal directive (reported by engineer Steve Yegge in 2011, describing a ~2002 mandate, with the usual caveats about secondhand accounts) required all teams to expose their data and functionality through service interfaces — no back doors.

The strategic leap, credited to Bezos and the team around him (notably Andy Jassy, then Bezos’s technical advisor/”shadow”), was to sell that infrastructure externally: computing as a utility, billed by the hour, no upfront commitment.

2006: S3 and EC2

• 14 March 2006: Simple Storage Service (S3) launches — effectively infinite storage over the internet.
• August 2006: Elastic Compute Cloud (EC2) launches — virtual servers on demand.

The pitch inverted enterprise IT: no procurement cycles, no capacity planning, pay for what you use. Startups — and eventually Netflix, Airbnb, NASA, the CIA — built on it.

The Jassy era

Andy Jassy led AWS from its inception, turning it into Amazon’s growth and profit engine; by the late 2010s AWS generated the majority of Amazon’s operating income despite being a minority of revenue. Jassy’s re:Invent keynotes became the cloud industry’s tentpoles. When Bezos stepped down as Amazon CEO in July 2021, Jassy succeeded him — the AWS builder inheriting the whole company.

Why it mattered

AWS did three things at once: it made Amazon’s retail infrastructure profitable twice over; it lowered the cost of starting a software company to near zero, fueling the startup boom; and it gave Amazon a high-margin business that subsidized the low-margin retail flywheel. Competitors (Microsoft Azure, Google Cloud) followed the model Bezos’s team defined.

Criticisms and disputes

• Open-source tensions: AWS has been criticized for commercializing open-source projects (e.g., Elasticsearch) without contributing proportionally; AWS disputes the framing and cites contributions and its own open-source work (e.g., Firecracker, Bottlerocket).
• Market dominance: AWS’s ~30% share of cloud infrastructure has drawn regulatory attention alongside the broader Big Tech scrutiny; the facts of market share are reported, the interpretations contested.
• The API-mandate story (Yegge’s 2011 post) is secondhand and lightly disputed in its details; this site treats it as reported, not gospel.

Source notes

• Internal-infrastructure origins, ~2003 standardization, Jassy’s role: The Everything Store (Stone, 2013), Working Backwards (Bryar & Carr, 2021); see aws-origins.md.
• API-mandate account: Steve Yegge, “Stevey’s Google Platforms Rant” (2011) — secondhand; flagged as reported.
• S3 (14 March 2006) and EC2 (August 2006) launch dates: Amazon/AWS records; see aws-origins.md.
• AWS share of operating income: Amazon SEC filings (10-K), various years.
• Open-source disputes (Elasticsearch fork/OpenSearch, 2021): contemporaneous tech press; AWS’s contributions cited from AWS public statements.

Limitations

• Cloud market-share figures move quarterly and vary by analyst (Gartner, Synergy); this page avoids standing figures — see methodology.md.