Six Reasons Cloud Wins vs. Traditional Infrastructure
Andy Jassy's original re:Invent pitch for why enterprises should move to AWS.
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 85%
At the very first AWS re:Invent in 2012, Andy Jassy presented a simple six-point framework explaining why cloud infrastructure beats traditional on-premises infrastructure for enterprises. The argument moves from financial structure (trading capex for opex) to raw economics (lower costs via AWS's scale) to operational flexibility (no need to guess capacity, ability to scale down without stranded assets) to talent leverage (engineers focus on code, not infrastructure) to reach (instant global presence). This became one of the most repeated enterprise sales frameworks in cloud computing history and is a reusable scorecard for pitching any infrastructure-as-a-service offering against legacy alternatives.
Origin
Presented by Andy Jassy at the first AWS re:Invent conference in 2012 as part of AWS's enterprise sales pitch.
Core principles
- 01Reframe capital expense as operating expense to unlock budget flexibility
- 02Economies of scale from a shared provider beat self-run infrastructure economics
- 03Elasticity removes the need for capacity forecasting
- 04Engineering time is a scarcer resource than compute — protect it
- 05Global reach should be a checkbox, not a multi-year infrastructure project
How to run it
- 1
Trade Capex for Opex
Position cloud spend as an operating expense taken each year on the income statement rather than a large upfront capital expenditure that must be capitalized and depreciated.
- 2
Show Lower Opex via Economies of Scale
Demonstrate that AWS's massive purchasing scale results in lower effective infrastructure costs passed on to the customer than they could achieve running their own hardware.
- 3
Remove the Need to Guess Capacity
Highlight that elastic infrastructure scales up automatically as demand grows, removing the risk of over- or under-provisioning ahead of time.
- 4
Allow Scaling Down Without Stranded Costs
Point out that when a project doesn't work out, the customer isn't stuck with legacy hardware they already paid for — they simply stop paying.
- 5
Free Engineers to Focus on Code
Argue that engineering time spent racking servers and managing data centers is time not spent building differentiated product — cloud infrastructure reclaims that time.
Pro tip Tie this back to the 'make your beer taste better' principle when pitching internally.
- 6
Deliver Instant Global Reach
Emphasize that customers get access to a global infrastructure footprint immediately, rather than building out their own data centers region by region.
Watch out Global availability isn't automatic by default for every service — some resources are still region-specific, so verify architecture assumptions.
In the wild
NASA became an AWS customer around 2009, using the platform for data streaming and video distribution during the Mars landing coverage, an early proof point of enterprise and government-grade reliability.
→ Helped establish AWS's credibility with large institutional customers.
Netflix CEO Reed Hastings, interviewed on stage at the first re:Invent, stated plainly that using AWS was simply the smart infrastructure decision for Netflix, despite competing with Amazon in other areas.
→ The endorsement became a major credibility signal that helped convince other skeptical enterprises to adopt AWS.
Common mistakes
Overpromising Instant Global Consistency
AWS originally implied data could be globally replicated by default, but had to walk this back — customers don't get one global availability zone automatically, and bandwidth constraints are real.
Ignoring Switching Costs When Pitching Migration
The six-reasons pitch focuses on the benefits of moving but glosses over the very real lock-in costs customers take on once their data lives in a given cloud.
Treating It as a One-Time Pitch
Enterprise buyers need this value reinforced repeatedly as competitive options (like multi-cloud) emerge, not just convinced once at the start of the relationship.
Is it for you?
Best for
Sales teams or IT leaders building the business case for cloud migration to skeptical enterprise stakeholders.
Not ideal for
Highly regulated environments with legal or data-sovereignty requirements that make any cloud migration currently infeasible.
From the transcript
“he has a great slide on this where he talks about the six reasons aws wins versus traditional infrastructure for enterprises”
“one you're trading capex for opex which is great you can take all that expense in every income statement every year as opposed to capitalizing…”
From the episode
Amazon Web Services