- Joined
- Aug 20, 2006
- Messages
- 13,000
The massive outage that occurred earlier this week (Tuesday) is being blamed on a sloppy employee who entered an incorrect command (fatty fingers?) as he was trying to remove a small number of servers. As everyone knows, a lot more than that ended up going offline. I take it that the AWS department has a new opening? Not sure I would be able to handle looking Bezos in his creepy eyes, though...
"The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected," the company noted. "At [12:37 p.m. ET], 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. "Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended," the message added.
"The Amazon Simple Storage Service (S3) team was debugging an issue causing the S3 billing system to progress more slowly than expected," the company noted. "At [12:37 p.m. ET], 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. "Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended," the message added.