Author here. > Your master access to S3 should never go into your servers. Create an IAM access with authorization to only PUT objects into S3. Isn't this pre

Author here. > Your master access to S3 should never go into your servers. Create an IAM access with authorization to only PUT objects into S3. Isn't this precisely the approach I take in the article? But, you need to make sure the master access to S3 is not compromised as well. Probably obvious, but certainly not wrong. > End note: this is still not enough. An attacker could compromise your backup script and wait for 40 days before locking yourself out of your data. When you try to recover a backup, you'll notice you have none. I agree that's a reasonable attack scenario. Just as for any backup strategy, you'd need a monitoring strategy (i.e. try restoring a backup at least every X days), and that was left as an exercise at the end of the post.