We work with a lot of companies (especially in the finance industry) that have strict rules around the minimum time data needs to be kept for. This can become quite onerous and expensive if you need to keep customer records for a minimum of 7 years, for example.
Using S3, Glacier, and life cycle rules, we can create a flexible long-term backup solution while also automating the archiving and purging of backups and reducing costs.
We are also going to utilize versioning in order to mitigate the damaged caused by a file being accidentally deleted or overwritten in our backup bucket.
- First, we need to define a few parameters:
ExpirationInDays: This is the maximum amount of time we want to have our files kept in backup for. We've set a default for this value of 2,555 days (7 years).TransitionToInfrequentAccessInDays: After a backup has been copied to S3, we want to move it to the infrequently accessed class to reduce our costs. This doesn't affect the...