Summary of the Amazon S3 Service Disruption

Re:Summary of the Amazon S3 Service Disruption by vocatus_gate on Thursday March 02, 2017 @02:28PM (#13777353)

I once brought down our entire production XenServer cluster group by issuing a "shutdown now" in the wrong SSH window. Needless to say it was a bad feeling watching Nagios go crazy and realizing what had just happened.

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by Piskvorrr on Thursday March 02, 2017 @05:14PM (#13778773)

    root@baz # shutdown now
    W: molly-guard: SSH session detected!
    Please type in hostname of the machine to shutdown: foo
    Good thing I asked; I won't shutdown baz ...

Surprising to see such a simple protection neglected.

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by twunde on Thursday March 02, 2017 @07:15PM (#13779654)

I don't know how well-known molly-guard is, but I've never heard of it before. Definitely enabling it on my servers next week.

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by Piskvorrr on Friday March 03, 2017 @02:58PM (#13785795)

Interesting. Up until now I've considered it well-known to the point of ubiquity :)

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by gigatexal on Thursday March 02, 2017 @03:22PM (#13777812)

Oh crap! Yeah I bet you were pretty panicked. My update statement destroyed data that my team used all the time so I was worried I'd get fired. Luckily that wasn't the case.

[ Parent | on HN ]