While I reflected on some Enterprise based use and benefits. However, my personal interest lies in using AWS Glacier for providing long archival storage for personal data (photos, videos, and music).
Notes from AWS S3 documentation:
- Amazon S3 will archive objects for you and associate those objects with the Glacier storage class according to rules that you define.
- When you transition objects to the Glacier storage class, AWS S3 internally uses AWS Glacier for durable storage at lower cost.
I’ve used the following transition rule:
I’ve been able to confirm the following events work seamlessly:
- Items with ‘Storage Class – Glacier’ are not overwritten | re-copied by the scheduled back up process to the S3 bucket.
- Deleting items – delete in the S3 bucket and the Glacier vault.
- Overwriting a file (same filename), re-creates it in the S3 bucket, and then it is transitioned to Glacier as per the rule sets.
- The Prefix setting needs to use the full directory | folder structure in the target S3 bucket to the location of the target files.
I will now start transitioning my other S3 bucket stores from AWS S3 – RRS to AWS Glacier. I will track the charges and costs of storage and data transfer as this process goes forward, I do anticipate a spike in data transfer costs for the bulk migration of content from AWS S3 – RRS to AWS Glacier.
Are you thinking of using the AWS Glacier service?