Amazon Web Services
Featuring Jeff Bezos
By the early 2000s, Amazon's engineers were burning weeks of effort spinning up compute, storage, and databases for every new project. So they built a standardized set of internal infrastructure services with clean APIs to make themselves faster. In 2006, Amazon flipped that internal plumbing into public products, S3 and EC2, and let any developer rent computing power by the hour. Within a few years a side effort was quietly outearning the retail business that spawned it.
This is the rare case where a company's cost center became its profit engine, and the question it forces is uncomfortable: how do you tell the difference between a tool you built to survive and a product the whole market would pay for? Founders and operators sitting on hard-won internal capabilities will recognize the tension. The case sharpens the instinct for spotting an asset hiding in plain sight, without handing you the rule for when to sell it.
Frequently asked questions
What is the Amazon Web Services origin story?
Amazon Web Services began as internal infrastructure that Amazon's engineers built to stop wasting weeks spinning up compute, storage, and databases for every project. They created a standardized set of internal services with clean APIs to move faster, and in 2006 Amazon turned that internal plumbing into public products, S3 and EC2. Within a few years AWS was quietly outearning the retail business that spawned it.
When did Amazon launch S3 and EC2?
Amazon launched its public cloud products S3 and EC2 in 2006, letting any developer rent computing power and storage by the hour. These grew out of internal infrastructure services Amazon had built for itself in the early 2000s. The launch effectively created the modern infrastructure-as-a-service market.
Why did AWS become so successful?
AWS succeeded because Amazon recognized that internal infrastructure it had built to survive was something the whole market would pay to rent. By turning a cost center into a product with clean APIs and hourly pricing, Amazon reached developers and startups who could not build that infrastructure themselves. The business carried high margins and scaled into Amazon's profit engine.
What can founders learn from how AWS was created?
The lesson is to look at hard-won internal capabilities and ask whether a tool you built just to survive is actually a product the whole market would pay for. AWS shows that an enormously valuable asset can hide in plain sight as internal plumbing. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.