"Deep Dive: The Origins of AWS"
From internal plumbing to the industry's foundation — the full origin story of the cloud.
The problem (2002–2003)
As Amazon’s retail systems grew, every team rebuilt the same undifferentiated infrastructure — databases, queuing, storage. Development slowed as coordination costs rose. Around 2003, Amazon began a systematic effort to factor the company’s infrastructure into standardized, reusable services.
The mandate
Engineer Steve Yegge’s famous 2011 post describes a Bezos directive from around 2002: all teams will henceforth expose their data and functionality through service interfaces — no direct database access, no back doors; teams communicate through these interfaces, “no exceptions.” The account is secondhand and its details are lightly disputed, but the architectural outcome is not: Amazon rebuilt itself as services talking to services. That internal discipline became the product.
The leap
The strategic insight, developed by Bezos with Andy Jassy (then his technical advisor, known as his “shadow”) and the early AWS team: the infrastructure Amazon needed for itself was infrastructure every company needed — and Amazon could sell it as a utility. The pitch inverted enterprise IT economics: no upfront servers, no procurement, pay by the hour.
2006: the launches
- 14 March 2006 — S3 (Simple Storage Service): effectively unlimited storage over the internet, priced per gigabyte.
- August 2006 — EC2 (Elastic Compute Cloud): virtual servers on demand.
Early adopters were startups that couldn’t have existed otherwise — the capital cost of a data center fell to a credit card. Then came the enterprises, then governments (including, notably, a 2013 CIA cloud contract worth a reported $600M, a landmark enterprise win).
The Jassy build-out
Jassy ran AWS from inception, and his annual re:Invent keynotes (the conference launched 2012) became the industry’s roadmap events: new services by the dozen, each year. By the late 2010s, AWS was generating the majority of Amazon’s operating income — the high-margin engine funding the low-margin retail flywheel. The student had become the company’s economic center.
The succession
When Bezos stepped down as Amazon CEO on 5 July 2021, the successor was Jassy — the AWS builder, at Amazon since 1997. The choice ratified what the numbers had said for years: the side project was the company.
Source notes
- Internal infrastructure problem, ~2003 standardization effort, Jassy/”shadow” role, utility-computing insight: The Everything Store (Stone, 2013); Working Backwards (Bryar & Carr, 2021).
- API-mandate account: Steve Yegge, “Stevey’s Google Platforms Rant” (2011) — secondhand; flagged as reported, details lightly disputed.
- S3 (14 March 2006), EC2 (August 2006): AWS records.
- CIA contract (2013, reported ~$600M): contemporaneous reporting.
- re:Invent (launched 2012): AWS records. AWS share of operating income: Amazon 10-K filings.
- Jassy succession (5 July 2021): Amazon announcement.
Limitations
- Early AWS deliberations rest on participant accounts and reporting; Amazon disclosed little contemporaneously.