Techdirt Podcast Episode 112: When A Typo Breaks The Internet

from the AW(OO)S dept

Tue, Mar 7th 2017 1:15pm — Leigh Beadon

From its humble origins as an online bookseller that many people worried might not survive, Amazon has grown into a critical piece of the web's backbone via its Amazon Web Services platform. Last week's S3 outage made this painfully clear, and understandably raised lots of concerns — especially after it was revealed that the whole thing was caused by a typo. So this week we're discussing whether something needs to be done, and what that might be.

Follow the Techdirt Podcast on Soundcloud, subscribe via iTunes or Google Play, or grab the RSS feed. You can also keep up with all the latest episodes right here on Techdirt.

Filed Under: aws, internet, podcast, s3
Companies: amazon

3 Comments

If you liked this post, you may also be interested in...

Reader Comments

Subscribe: RSS

View by: Time | Thread

David (profile), 7 Mar 2017 @ 2:21pm

Did any of you read Amazon's statement?
Too many S3 servers were shutdown. Then various command structures failed as a result. S3 had to restart and that took much, much longer than expected. So the typical cascading errors took place.

Read their post. They have addressed the problem with the tools such that S3 will not allow the minimum number of servers required be removed.
[ link to this | view in chronology ]
Anonymous Coward, 7 Mar 2017 @ 2:45pm

from the AW(OO)S dept

That'll be $350 dollars, Leigh.
[ link to this | view in chronology ]
Lawrence D’Oliveiro, 7 Mar 2017 @ 3:53pm

Don’t Talk To Me About Typos
I eat missing dots in bind configs for breakfast.
[ link to this | view in chronology ]