Door locks, TV remotes, light controllers, front gate IoT openers, IoT mouse (Razer), Nest’s security cameras, thermostats, and a ton of smartphone apps. Adobe’s cloud, Zoom.us, Zendesk, Salesforce, Heroku, Coursera, Bitbucket, Autodesk’s cloud, Twilio, Mailchimp, Citrix, Expedia, Flipboard, and Yahoo! Mail, Docker’s Registry Hub, Trello, Travis CI, GitHub, GitLab, Quora, Medium, Signal, Slack, Imgur, Twitch.tv, Razer, Xero, SiriusXM, and Strava, media publications that stored images and other media in S3 were all DOWN for 6 hours.
For those of you who don’t think about these things, life is simple. For the rest of us who uses #AWS, it’s one big scary thing. And that was just a small part of the cloud. Imagine if all of AWS went down.
Personally, because I manage a large number of sites using EC2 and S3, it was one of the most confusing day. The first 2 hours were just excruciatingly stressful as 10,000++ emails were coming out that day and I didn’t know what was wrong as the AWS status dashboard didn’t show there was something wrong so I had to look and made check points elsewhere.
The dashboard not changing color is related to S3 issue. See the banner at the top of the dashboard for updates.
— Amazon Web Services (@awscloud) February 28, 2017
Panic, fear, confusion was just the start of it. There is an urgent need for redundancy in cloud computing.
UPDATE: Super short summary: An engineer made a typo in a COMMAND.