The Typo That Took Down the Cloud
On February twenty-eighth, twenty seventeen, a routine maintenance command at Amazon Web Services was entered with a single incorrect parameter. This is the story of how one mistyped input triggered a cascading failure that paralyzed a massive slice of the internet for hours.
Listen in the Fylom app.
A mistyped command parameter on February twenty-eighth, twenty-seventeen, paralyzed the entire us-east-one AWS region.
The outage lasted nearly four hours because the system scale exceeded its original startup recovery capacity.
AWS status page icons failed to load because they were hosted on the very service that crashed.
The failure acted like a library losing its card catalog, requiring a manual scan of every data byte.
A circular dependency prevented engineers from using diagnostic tools that relied on the broken S3 infrastructure.
The collapse proved that a single human error can disable physical security systems and global digital services.
- 01Intro1 min
- 02The Command and the Collapse3 min
- 03The Cascading Effect2 min
- 04The Long Road Back2 min
- 05The Fragility of the Invisible2 min
- 06Outro1 min
- Summary of the Amazon S3 Service Disruption in ...
- The 2017 S3 Outage: A Typo That Broke the Web - Lessons That…
- Amazon And The $150 Million Typo
- AWS Outage that Broke the Internet Caused by Mistyped ...
- After the Retrospective: The 2017 Amazon S3 Outage - Gremlin
- Amazon AWS S3 outage is breaking things for a lot of ...
- Post-Event Summaries
- How did a single mistyped command by one AWS ...
- Why a Single Command Took Down Azure: The Myth of "Human Error"
- Global Network Post-Mortem | IAExplore
- About the 5-hour Microsoft Outage
Fylom generates episodes like this on any topic you're curious about.
Fylom episodes are researched, written, and voiced by AI. Automated checks help catch inaccuracies, but episodes aren't reviewed by a human and AI can still get things wrong. Treat them as a starting point, not a source of record — more in our accuracy disclaimer.