Why it matters
Manual snapshots are kept forever unless someone deletes them, so their cost only grows.How nOps finds it
nOps reads the last 30 days of RDS billing for each database that was still billed in the last 3 days and has available snapshots. A database is flagged when its snapshot storage cost more than $100 in those 30 days and more than 5% of the database’s total cost. The saving is the snapshot cost minus 5% of the database’s total cost. The recommendation counts the database’s automated, AWS Backup and manual snapshots.Before you start
Permission to delete snapshots and modify the database (rds:DeleteDBSnapshot, rds:ModifyDBInstance), or to change the AWS Backup plan. Know your restore and compliance requirements.
How to implement
- List the database’s snapshots:
aws rds describe-db-snapshots --db-instance-identifier NAME. - Delete manual snapshots that are no longer needed:
aws rds delete-db-snapshot --db-snapshot-identifier ID. - If automated backups dominate, lower the backup retention period: RDS → Databases → Modify → Backup retention period.
- If AWS Backup recovery points dominate, shorten the retention in the backup plan’s lifecycle.
- Export snapshots you must keep long term to S3, or keep them in a cheaper archive, before deleting them.
Risks and considerations
- Deleted snapshots cannot be recovered, and a shorter retention period removes older restore points.
- The 5% target is a rule of thumb, not a requirement. Keep what your recovery and compliance needs demand.
FAQs
Why 5% of the database cost?
Why 5% of the database cost?
It is the level nOps treats as normal snapshot overhead. The saving shown is only the snapshot cost above it.