5 Lessons to Learn from the Big Amazon Crash of 2017

5 Lessons to Learn from the Big Amazon Crash of 2017

On February 28, 2017, the world saw what happens when a giant cloud company’s servers suddenly stop working. It all started around 9:30 a.m. PST when websites using Amazon Web Services’ S3 cloud storage servers noticed that something was not right. Soon after, some of the biggest applications and websites experienced total crashes.

“S3 is experiencing high error rates. We are working hard on recovering.”
— Amazon Web Services (@awscloud) February 28, 2017

Popular websites like Slack, Trello, Giphy, Medium and even Amazon’s own ability to report the problem was partially or completely down for about 5 hours. Were you among the affected?

If your business uses any of the popular third-party applications that help with collaboration or online storage, then chances are you, too, felt handicapped following the crash. The impact was felt by many because Amazon controls 40 percent of the cloud market and has a clientele list that includes some of the world’s largest organizations in the world.