5 ms·
> No, the automatic 7 day RDS snapshots or turning on S3 versioning is not a sufficient backup. Neither is mirroring to a S3 Glacier bucket in the same org, or
by tomrod 6y ago
> No, the automatic 7 day RDS snapshots or turning on S3 versioning is not a sufficient backup. Neither is mirroring to a S3 Glacier bucket in the same org, or rsyncing to a a backup server in the same datacenter.
Why?
- danielheath 6y agoA few reasons come to mind. If you lose control of an aws root account it can take weeks to get it back. That’s probably enough time for the hackers to clean out the backups. Billing issues can lead to aws wiping out an account. For $work the backups are in AWS but using a different payment method, account owner etc to prevent cross contamination. Honestly, they should be outside aws entirely, but separate accounts is a good start.
- viraptor 6y ago> If you lose control of an aws root account it can take weeks to get it back. > Billing issues can lead to aws wiping out an account. These are small-scale related issues though. When you're at the level where it's hard to have a reasonable backup outside of AWS, you can also resolve the root account issues fairly quickly by calling your TAM directly.
- deleted 6y ago[deleted]
- tooltower 6y agoBecause they share the failure domain. In all of those cases, there's a single point of failure.