Techdirt Podcast Episode 112: When A Typo Breaks The Internet

from the AW(OO)S dept

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.

Hide this

Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.

Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.

While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.

–The Techdirt Team

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


Reader Comments

Subscribe: RSS

View by: Time | Thread


  • icon
    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 ]

  • identicon
    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 ]

  • identicon
    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 ]


Follow Techdirt
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Discord

The latest chatter on the Techdirt Insider Discord channel...

Loading...
Recent Stories

This site, like most other sites on the web, uses cookies. For more information, see our privacy policy. Got it
Close

Email This

This feature is only available to registered users. Register or sign in to use it.