I think people are overthinking this. I'm the first one to criticize AWS (I run a competitor, carolinacloud.io) but I don't think we should hold it against them when they lost data due to their hard drives being physically bombed.
The surprising thing is that multiple availability zones were bombed simultaneously.
And to my knowledge, they haven’t even yet said 2+ AZs were compromised.
> https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...
They are far enough apart that tornados, floods, and fires cannot simultaneously impact multiple.
But AFAIK AWS has only reported data loss in mec1-az2.
Cross-AZ services like S3 should have no data loss, unless there is more damage than AWS has currently published.
It's like saying "Oh this car manufacturer claimed that their cars were the safest in the industry but couldn't prevent this driver from flying through the windshield" and omitting the fact the person wasn't wearing a seatbelt.
No one was forcing Amazon to make deals with oligopolies and monarchies in the middle east.
No one was forcing Amazon to engage with US imperialism.
Like these things have extremely large threads connecting to one another. Now AWS, along with other American big tech companies, are legitimate military targets. This is what happens when you engage in these practices. You don't get to serve the interests of US imperialism and claim you're innocent. They deliberately signed up for this, there is a long history of this in US imperialism. It's nothing new.
Next time you don't want missiles raining down upon your data center, don't engage yourself in imperial politics. You won't be shocked next time when someone punches you in a face.