Amazon Web Services

Amazon Web Services

AcquiredSep 6, 20222h 49m

David Rosenthal (host), Ben Gilbert (host)

AWS profitability vs Amazon retailFour AWS origin storiesWeb 2.0, APIs, and “hardened interfaces”Service-oriented architecture and internal platformingLaunch of key primitives: S3, EC2, CloudFront, RDSStartups → enterprise adoption playbookWhy incumbents missed cloud (Oracle/IBM/Microsoft/Google)Database stickiness and migration lock-inUtility-scale economics and price cutsAWS gaps: Redshift vs Snowflake, product sprawl

In this episode of Acquired, featuring David Rosenthal and Ben Gilbert, Amazon Web Services explores how AWS emerged from Amazon’s internal pain to dominate cloud computing Acquired explores how Amazon Web Services grew from internal infrastructure and organizational bottlenecks into the dominant cloud computing utility powering much of the internet.

How AWS emerged from Amazon’s internal pain to dominate cloud computing

Acquired explores how Amazon Web Services grew from internal infrastructure and organizational bottlenecks into the dominant cloud computing utility powering much of the internet.

The hosts debunk the popular “excess capacity” myth and present four overlapping origin stories, emphasizing Amazon’s API-first, service-oriented architecture mandate and Andy Jassy’s leadership in productizing infrastructure for external developers.

They explain why AWS’s early primitive building blocks (S3, EC2, later RDS/CloudFront) unlocked startups and then enterprises, while incumbents like IBM/Oracle, and later Microsoft/Google, stumbled for distinct strategic reasons.

The episode closes with an analysis of AWS’s durable competitive advantages (scale, switching costs, counterpositioning), a rare missed opportunity (Snowflake/data warehousing), and reflections on Amazon’s long-term cash flow and reinvestment model.

Key Takeaways

AWS wasn’t “selling spare servers”—it was a deliberate new business.

Werner Vogels explicitly calls the excess-capacity story a myth; AWS was designed as a standalone business expected to rival retail, and it would have exhausted any “spare” capacity quickly.

Get the full analysis with uListen AI

APIs were the cultural and technical bridge from retail to cloud.

Tim O’Reilly’s Web 2. ...

Get the full analysis with uListen AI

Service-oriented architecture solved an org-scaling problem as much as a code problem.

Amazon’s monolith and code freezes reflected brittle coupling; forcing teams to interact only through networked services reduced N² coordination and enabled independent shipping at scale.

Get the full analysis with uListen AI

Cloud primitives won because they matched real developer and enterprise constraints.

Starting with basic building blocks (storage/compute) let startups move fast and let enterprises later “lift and shift,” avoiding the too-early platform-first traps Microsoft and Google initially pursued.

Get the full analysis with uListen AI

AWS created a new buying motion: instant procurement and metered usage.

Credit-card provisioning removed RFPs, vendor negotiations, and data-center lead times—compressing build cycles from months to days and enabling the startup/hackathon era of rapid product iteration.

Get the full analysis with uListen AI

Incumbents lost because cloud counterpositioned their profit engines.

Oracle/IBM’s high-margin licensing and upgrade annuities discouraged pay-as-you-go primitives; Microsoft’s internal power centers and premature PaaS bet delayed a credible IaaS response; Google lacked enterprise sales muscle and appetite for “hard,” lower-margin operations.

Get the full analysis with uListen AI

Switching costs in cloud are real—especially in databases and data gravity.

Databases are sticky and data transfer is slow/expensive (Snowball/Snowmobile exist because WAN bandwidth lags data growth); even Amazon took until 2019 to fully migrate off Oracle internally.

Get the full analysis with uListen AI

AWS’s scale economics are utility-like and self-reinforcing.

Massive fixed costs spread across a huge base enable lower prices and continued capex; frequent proactive price cuts helped lock in demand confidence for further buildout—similar logic to other capex-heavy scale businesses.

Get the full analysis with uListen AI

AWS’s biggest product miss is the independent rise of Snowflake.

Despite Redshift, Snowflake became a major standalone data-warehouse company on top of cloud providers, suggesting AWS struggled to deliver a simpler, developer-delighting warehouse experience amid enterprise constraints and legacy framing.

Get the full analysis with uListen AI

Operational excellence now coexists with platform lock-in and margin expansion.

AWS began as unopinionated primitives but increasingly nudges customers to higher-level managed and proprietary services (e. ...

Get the full analysis with uListen AI

Notable Quotes

“The excess capacity story is a myth.”

Werner Vogels (quoted by hosts)

“All teams will henceforth expose their data and functionality through service interfaces… Anyone who doesn’t do this will be fired.”

Jeff Bezos mandate (quoted via Steve Yegge post)

“If you believe developers will build applications from scratch using web services as primitive building blocks, then the operating system becomes the internet.”

Andy Jassy (as recounted by hosts)

“A credit card was all that was needed to provision storage… my bill… was $3.08… the following month… $0.07.”

James Hamilton (quoted by hosts)

“I believe that AWS is market size unconstrained.”

Jeff Bezos (quoted by hosts)

Questions Answered in This Episode

Among the four origin stories, which events were truly causal versus just enabling context (APIs, SOA mandate, IT-as-API, Pinkham/Black memo)?

Acquired explores how Amazon Web Services grew from internal infrastructure and organizational bottlenecks into the dominant cloud computing utility powering much of the internet.

Get the full analysis with uListen AI

What specific internal technical constraints at Amazon made “IT-as-an-API” necessary, and how did that map to the external S3/EC2 product design?

The hosts debunk the popular “excess capacity” myth and present four overlapping origin stories, emphasizing Amazon’s API-first, service-oriented architecture mandate and Andy Jassy’s leadership in productizing infrastructure for external developers.

Get the full analysis with uListen AI

Why did AWS choose primitives first instead of a full PaaS approach, and what would a “too-early” AWS have looked like if they’d started with Lambda-like abstractions in 2006?

They explain why AWS’s early primitive building blocks (S3, EC2, later RDS/CloudFront) unlocked startups and then enterprises, while incumbents like IBM/Oracle, and later Microsoft/Google, stumbled for distinct strategic reasons.

Get the full analysis with uListen AI

How did AWS build enterprise sales and procurement capabilities from a credit-card-first motion—what were the first repeatable enterprise playbooks (academia/NASA/CIA, billing/discounting, re:Invent)?

The episode closes with an analysis of AWS’s durable competitive advantages (scale, switching costs, counterpositioning), a rare missed opportunity (Snowflake/data warehousing), and reflections on Amazon’s long-term cash flow and reinvestment model.

Get the full analysis with uListen AI

Is AWS best understood today as IaaS, a managed-services platform, or a portfolio of utilities—and how does that framing affect competitive strategy versus Azure/GCP?

Get the full analysis with uListen AI

Transcript Preview

David Rosenthal

People, turns out, loved the amazon.com episode. That was so awesome. Makes me a little nervous for this one.

Ben Gilbert

Oh, massively. By far and away, our biggest episode ever. Uh, is this how George Lucas felt when he was doing Empire Strikes Back? [laughing]

David Rosenthal

[laughing] You did not just compare us to George Lucas, did you? [laughing] I swear we're humble.

Ben Gilbert

All right, let's do this.

Speaker

Who got the truth? Is it you? Is it you? Is it you? Who got the truth now? Is it you? Is it you? Is it you? Sit me down, say it straight, another story on the way. Who got the truth?

Ben Gilbert

Welcome to Season 11, Episode 3 of Acquired, the podcast about great technology companies and the stories and playbooks behind them. I'm Ben Gilbert, and I am the co-founder and managing director of Seattle-based Pioneer Square Labs, and our venture fund, PSL Ventures.

David Rosenthal

And I'm David Rosenthal, and I am an angel investor based in San Francisco. Cold San Francisco, here in August. [chuckles]

Ben Gilbert

[chuckles] And we are your hosts. All right, David, let's say you run a lemonade stand. You sell me the highest quality lemonade you can for the lowest price, one dollar a cup, and when you add up all your costs, the variable ones, like the lemons, and the fixed ones, like the table that you rented, it costs about ninety-eight and a half cents to give me that lemonade. And you're happy with your turn to profit, I'm sure, but man, you are gonna have to sell a lot of lemonade.

David Rosenthal

So you're telling me I'm amazon.com in the fourth quarter of two thousand and one, which is actually where we're gonna start our story.

Ben Gilbert

Perhaps. But you discover something interesting. By making all this lemonade, you get really good at the stuff it takes to run a lemonade business, the perfect cups, and ice, and lemons, everything, and it turns out, all that stuff that you just got good at, you can sell to other businesses. And guess what? You realize further that when you sell your services to other companies, when you charge them a dollar, it only costs you seventy cents to make it. So thirty percent margins instead of something like a percent and a half, you're gonna have to sell a lot less of those services than you ever did on lemonade to make the same amount of money.

David Rosenthal

Well, then, if you told me that, I would dig into it even further, and I would realize that the existing companies that sold stands, and cups, and whatnot, they were actually making seventy percent margins on their stands and cups. [chuckles]

Ben Gilbert

[chuckles]

David Rosenthal

And so I would be quite happy to take thirty percent margins and disrupt them, and still do better than my lemonade business.

Ben Gilbert

Well, listeners, of course, on our last episode, we talked about Amazon's retail business, and today, we are talking about Amazon Web Services, the cloud computing pioneer, and those margin percentages that I just used are the real ones for the retail business and for AWS. AWS's revenue is only about fifteen percent the size of Amazon's massive retail business, but their profits, or the operating income, to be specific, from AWS, are, in total, the same, if not more, than their e-commerce store. I think it's the case that every year since twenty fifteen, when they started breaking out AWS's financials, the total operating income from AWS has actually been bigger than [chuckles] the retail business.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome