No. That was operational modification of system state using existing tools. The “miss” was an intended subset filter that was not interpreted correctly.
> 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.
As of a while back that entire state management subsystem, which dates from the very beginning of AWS, has been replaced.
Source: me. I was oncall for (some of) the incident management of that event.
No. That was operational modification of system state using existing tools. The “miss” was an intended subset filter that was not interpreted correctly.
> 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.
As of a while back that entire state management subsystem, which dates from the very beginning of AWS, has been replaced.
Source: me. I was oncall for (some of) the incident management of that event.