I read an article a few years back about a company who'd had their AWS root account hacked and held for ransom [1] and even though they had backups and snapshots and multi-AZ replication the attacker could destroy the primary and the backups at the same time, because they were all in the same AWS account.
If the writers are imagining something so severe it could trigger a global depression, they're probably thinking of something with that kind of impact hitting everyone in the region.
Such an event would be very unlikely, you would hope - but I'm sure you could pull it off with the resources of a nation-state and half a dozen sleeper agents.
> even though they had backups and snapshots and multi-AZ replication the attacker could destroy the primary and the backups at the same time, because they were all in the same AWS account.
This was back in 2014, but AWS now has ways to fix this (if you do insist on keeping stuff in AWS) with Object Lock[0]. The expense is that, with object lock in a compliance state, the only way to delete it is to close the AWS account (which is why MFA delete[1] is recommended).
I'd like to know more about the nuances of this blanket statement:
>The best case outcomes closely resembled a global depression.