Except for the AWS EBS outage a couple of years ago which had nothing to do with a security breach.
http://aws.amazon.com/message/65648/
Cascading catastrophic failures do happen that don't involve security.
http://aws.amazon.com/message/65648/
Cascading catastrophic failures do happen that don't involve security.
Sudden shutdown of vital service + silence = most likely a security prob.
I'm not saying that's what it is but it seems likely.
IMO not communicating with the outside world is a fail, but I've seen delays in this when small teams suddenly get swamped.
You're just making up a conspiracy theory here.
Really? With the multi-region AWS failure, Amazon was very reluctant to even confirm it was happening for a while, and didn't explain it for weeks afterwards.
> Sudden shutdown of vital service + silence = most likely a security prob.
Or alternatively, "oops, how much customer data have we accidentally irreparably destroyed?!" IIRC in the aforementioned AWS incident Amazon only really started talking when they had an idea of how many EBS volumes were irreparably corrupt.