> 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

> 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). 0: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/object... 1: https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiFactorAuthenticationDelete.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiF...