3 ms·
Object lock helps tick some regulatory boxes, but at least in the described scenario, enabling it isn't really going to protect you against many additional thre
by WatchDog 5y ago
Object lock helps tick some regulatory boxes, but at least in the described scenario, enabling it isn't really going to protect you against many additional threat models.
Simply using object versioning, and an IAM role with no delete permission is sufficient.
The biggest risk with using AWS for backups, is being compromised via a high-privilege IAM role.
If a role has s3:* permission, it can just remove the locks and delete the file.
- justin_oaks 5y agoIndeed. It'd be best to have another copy of the backup somewhere other than S3, or in S3 under a different AWS account. I worked for a company that had all their databases in AWS RDS and all their database backups as RDS backups stored in the same AWS account. A compromise of a single high-privilege account could cause that company to no longer have ANY data. I warned the higher-ups repeatedly that they needed more than one backup location. They didn't seem to care too much.
- alanfranz 5y agoYes. Cross account replication is the way to go for better protection.