Ensure there are no EBS snapshots older than a month

AWS Cost Optimization

To decrease the cost of your monthly AWS bill, make sure to review your AWS account for any AWS EBS snapshots that are older than 30 days and delete them. According to the retention period threshold, incremental snapshots that are older than 30 days should be removed.Since EBS snapshots are incremental, deleting older snapshots won't impact your ability to restore volume data from newer snapshots. This means you can keep only the necessary backup data, reducing your AWS monthly costs.


Here are the steps you can follow to remediate AWS EBS snapshots older than 30 days:

  1. Identify older snapshots: Determine which EBS snapshots are older than 30 days by reviewing the creation date of each snapshot in your AWS account.
  2. Evaluate snapshot importance: Evaluate the importance of each snapshot and make sure that you have a backup of any critical data before deleting it.
  3. Delete older snapshots: Once you have identified older snapshots that are no longer necessary, delete them from your AWS account.
  4. Automate snapshot deletion: Consider automating the process of deleting snapshots by creating a lifecycle policy that automatically removes snapshots that are older than a specific timeframe.
  5. Monitor and repeat: Monitor your AWS account regularly to ensure that you're not storing unnecessary snapshots and repeat the process as necessary.

By following these steps, you can reduce the cost of your AWS bill by removing unnecessary EBS snapshots while ensuring that you still have access to any critical data that you need to retain.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.