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.

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

Reader Comments

Subscribe: RSS

View by: Time | Thread

  1. 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.

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here

Subscribe to the Techdirt Daily newsletter

Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Insider Shop - Show Your Support!

Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Report this ad  |  Hide Techdirt ads
Recent Stories
Report this ad  |  Hide Techdirt ads

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

Email This

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