Wonder what happened to the poor slob who did that. He/She was unauthorized AND caused a pretty serious outage...
EDIT: derp, my bad, I read as "unauthorized" which was "authorized".
EDIT: derp, my bad, I read as "unauthorized" which was "authorized".
Anyway, to me this firstly sounds like a "tool" or command that was too powerful with not enough safeguards. Who knows, the command might even be ambiguous.
typos happen, if the system didn't stop them that's a design issue or accepted risk.
" 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. Unfortunately, one of the inputs to the command was entered incorrectly and a larger set of servers was removed than intended."
"Fire you? I just spent $10 million training you!"