Which solution will meet these requirements MOST cost-effectively?
Keep the daily snapshot in the EBS snapshot standard tier for 1 month. Copy the monthly snapshot to Amazon S3 Glacier Deep Archive with a 7-year retention period.
Continue with the current EBS snapshot policy. Add a new policy to move the monthly snapshot to Amazon EBS Snapshots Archive with a 7-year retention period.
Keep the daily snapshot in the EBS snapshot standard tier for 1 month. Keep the monthly snapshot in the standard tier for 7 years. Use incremental snapshots.
Keep the daily snapshot in the EBS snapshot standard tier. Use EBS direct APIs to take snapshots of all the EBS volumes every month. Store the snapshots in an Amazon S3 bucket in the Infrequent Access tier for 7 years.
Explanations:
While copying monthly snapshots to S3 Glacier Deep Archive is cost-effective, there is no native way to move EBS snapshots directly to S3 Glacier Deep Archive. EBS snapshots are stored within the EBS system, so using S3 Glacier would require custom processes.
Moving monthly snapshots to Amazon EBS Snapshots Archive provides a cost-effective, compliant storage solution with native integration for EBS snapshots. The archive tier significantly reduces storage costs over 7 years.
Storing monthly snapshots in the standard tier for 7 years is not cost-effective, as standard EBS snapshots are more expensive long-term compared to archived snapshots.
Storing snapshots in Amazon S3 requires additional conversion and custom management efforts, and EBS snapshots cannot be directly stored in an S3 bucket. EBS Snapshots Archive is more efficient and purpose-built for this use case.
I structure that the answer is:
Continue with the current EBS snapshot policy. Add a new policy to move the monthly snapshot to Amazon EBS Snapshots Archive with a 7-year retention period.