A command meant to take out a few servers took out far more, and services across a whole AWS region went down with S3 — and AWS couldn't even update its own status page. Why did it spread so far and take so long?
15 minMediumMembership isn’t open yet. The free lessons are open — 19 of them.
You guess first, then run the system and see if you were right.
On 28 February 2017, Amazon S3 — the storage service many sites and apps keep their files in — stopped answering in AWS's Northern Virginia region (US-EAST-1) for hours. Other AWS services in that region broke with it. For the first two hours AWS couldn't even update the service statuses on its own health dashboard. How does one storage problem go that wide?
Steps 2–7 are for members