Why it matters
Snapshots accumulate quietly, often through scripts or manual backups that nobody cleans up.How nOps finds it
nOps reads your EBS snapshot inventory and the last 30 billed days of snapshot charges. A snapshot is flagged when it was created more than 90 days ago and was still billed on your latest billed day. The estimate is what the snapshot cost over the last 30 billed days. There is no minimum saving.Before you start
Permission to delete snapshots (ec2:DeleteSnapshot). Know your backup retention and compliance rules.
How to implement
- Review the snapshot’s creation date, description and tags:
aws ec2 describe-snapshots --snapshot-ids ID. - Check that no registered AMI uses it:
aws ec2 describe-images --owners self --filters Name=block-device-mapping.snapshot-id,Values=ID. Deregister the AMI first if it is no longer needed. - Check it is not locked and not managed by AWS Backup or Data Lifecycle Manager. Change the retention there instead.
- Delete it: EC2 → Snapshots → Actions → Delete snapshot, or
aws ec2 delete-snapshot --snapshot-id ID. - To save more, consider moving snapshots you must keep to the EBS Snapshots Archive tier.
Risks and considerations
- Deleting a snapshot is permanent.
- Snapshots are incremental. Data still referenced by a later snapshot of the same volume is kept, so the saving can be lower than the snapshot’s billed cost.
- A snapshot used by a registered AMI cannot be deleted until the AMI is deregistered.
FAQs
Why might the saving be lower than shown?
Why might the saving be lower than shown?
Snapshots share unchanged blocks. Deleting an old one only frees the blocks no other snapshot uses.