| Title | Amazon S3-zure Cause: Half the Web Vanished Because an AWS Bod Fat-Fingered a Command | |
| Date | Saturday March 04 2017, @04:56AM | |
| Author | ||
| Topic | ||
| from the who-among-us-can-cast-the-first-stone? dept. | ||
Over at The Register Shaun Nichols has a cheeky take on what happened to Amazon S3 last week:
Amazon has provided the postmortem for Tuesday's AWS S3 meltdown, shedding light on what caused one of its largest cloud facilities to bring a chunk of the web down.
In a note today to customers, the tech giant said the storage system was knocked offline by a staffer trying to address a problem with its billing system. Essentially, someone mistyped a command within a production environment while debugging a performance gremlin.
"The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected. At 9:37AM PST, an authorized S3 team member using an established playbook executed a command which was intended to remove a small number of servers for one of the S3 subsystems that is used by the S3 billing process," the team wrote in its message.
"Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended. The servers that were inadvertently removed supported two other S3 subsystems."
Those two subsystems handled the indexing for objects stored on S3 and the allocation of new storage instances. Without these two systems operating, Amazon said it was unable to handle any customer requests for S3 itself, or those from services like EC2 and Lambda functions connected to S3.
As a result, websites small and large that relied on the cheap and popular Virginia US-East-1 region stopped working properly, costing hundreds of millions of dollars in losses for customers. It also broke smartphone apps and Internet of Things gadgets – from lightbulbs to Nest security cameras – that were relying on the S3 storage backend.
Do any of our Soylentils here use Amazon S3 and if so, were you impacted by the outage?
| Links |
printed from SoylentNews, Amazon S3-zure Cause: Half the Web Vanished Because an AWS Bod Fat-Fingered a Command on 2023-05-26 16:38:40