A mistake took down more S3 servers than it should, including two subsystems essential to S3 operation. That resulted in S3 failure, affecting the S3 service and other services depending on it. Normal functioning was restored in about four hours.
A mistake took down more S3 servers than it should, including two subsystems essential to S3 operation. That resulted in S3 failure, affecting the S3 service and other services depending on it. Normal functioning was restored in about four hours.
Rarely Amazon AWS fails but when it does the internet finds out about it and many are directly impacted. It was the case of the recent AWS S3 failure that took place on February 28th in the Northern Virginia (US-EAST-1) region. It was not just S3 functioning that was disrupted but also a number of AWS services that depend on it, including EC2, EFS, API Gateway, Athena, Cloudsearch, MapReduce and others. These services either had an increased number of errors in functioning or simply did not work at all.
During the four hour disruption, it was reported that Expedia, GitLab, GitHub, GroupMe, IFTTT, Medium, Nest, Quora, Slack, The Verge, Trello, Twitch, Wix and many others were either taken offline or severely affected by the glitch. Even Amazon’s Alexa had trouble working and the AWS status dashboard was not updated for about 2 hours.
