How Amazon Web Services — the trillion‑dollar cloud giant — was born

In just two decades since its founding, Amazon Web Services (AWS)—the cloud computing arm of globally renowned Amazon—has grown into a technology giant generating over $142 billion in annual revenue. How exactly was this cloud behemoth born?

It All Began with a “Math Problem”

Before AWS came into existence, Amazon engineers were spending 70% to 80% of their time on infrastructure management—servers, storage, and the like—leaving only 20% for product innovation. Andy Jassy, then Chief of Staff to Jeff Bezos, toured various departments and kept hearing the same refrain: “It took me three months just to figure out my computing solution.” The team began to wonder: If we could flip this equation and enable developers to spend 80% of their time creating value, just how fast could technological innovation accelerate? AWS was built precisely to answer that question.

The Vision That Attracted an MBA Intern

When current AWS CEO Matt Garman joined the company in 2005, the project was still in stealth mode. While other interns gravitated toward high-profile retail businesses like books and music, he was drawn to this mysterious opportunity—one that was “highly technical with enormous potential.” When he was hired in 2006 as AWS’s first product manager, the global sales team consisted of just three people. Wearing multiple hats, he wrote product descriptions, set pricing, and hosted naming meetings, helping to build Amazon EBS (Elastic Block Store), which remains a core service to this day.

AWS Was Born in a Pub!

Before the services launched, key design elements were sketched out in a bar. Amazon S3 (Simple Storage Service), introduced in March 2006, was conceived at the Six Arms pub on Seattle’s Capitol Hill. It was there that the team established a core principle: “The system should be as simple as possible, but not simpler.” They developed ten technical guidelines emphasizing decentralization and treating hardware failures as a matter of course—designing for failure from the very outset. This mindset gave birth to a global storage system that now holds over 500 trillion objects.

Five months later, another foundational service—Amazon EC2 (Elastic Compute Cloud)—went live, and its development journey similarly showcased the team’s resilience. Eight engineers were working from Cape Town, South Africa—more than 10,200 miles and roughly 10 time zones away from headquarters. Using nothing but a pile of laptops in a corner of their office, they successfully simulated a full-fledged data center architecture. They embraced the South African saying “‘n Boer maak ‘n plan” (a farmer always finds a way)—no matter the obstacle, a solution could be found. This pragmatic, can-do spirit laid the groundwork for the cloud computing revolution.

From an internal problem, an intern’s bold career move, sketches drawn in a pub, and a team’s unwavering commitment to remote development—these seemingly small decisions, two decades later, have become an indelible chapter in the history of technology.