Re:Summary of the Amazon S3 Service Disruption
by ehsankia on Thursday March 02, 2017 @01:04PM
(#13776492)
To me, the more important part would've been the solutions they'll come up with to avoid something like this happening again. Is it going to just be "add a line to the playbook asking the engineer to double check the command" or will they make big changes across the system to prevent things like this happening.
[ Parent
| on HN ]
Re:Summary of the Amazon S3 Service Disruption
by lovehashbrowns on Thursday March 02, 2017 @01:09PM
(#13776546)
I'm interested in something like that, too! I've got a few destructive Ansible commands that I check a few dozen times before running. But There's always a chance that I'm tired/distracted/whatever and run something silly anyway. Typically I put in things like config test checks and prompts, but damn it's scary how much power I have with this Ansible setup. I definitely don't want to be in this AWS position.