Re:Summary of the Amazon S3 Service Disruption
by cnorthwood on Thursday March 02, 2017 @12:19PM
(#13775928)
I'm surprised how transparent this is, I can find Amazon often a bit opaque when dealing with issues.
[ Parent
| on HN ]
Re:Summary of the Amazon S3 Service Disruption
by snewman on Thursday March 02, 2017 @12:30PM
(#13776068)
I've found them to be very opaque in most contexts, but for major outages (which have been rare), they do have a history of solid postmortems.
Re:Summary of the Amazon S3 Service Disruption
by DigitalBison on Thursday March 02, 2017 @01:24PM
(#13776685)
The public postmortem from the big DynamoDB outage in 2015(?) is a great example I think: https://aws.amazon.com/message/5467D2/
Re:Summary of the Amazon S3 Service Disruption
by edblarney on Thursday March 02, 2017 @01:01PM
(#13776464)
They have no choice in this situation.
CEO's all over the world just realized that they can't only depend on S3, and they might have to double up on their infrastructure and have a parallel env. on Azure or Google as well.