Orphaned EBS Snapshots
CostLens flags EBS snapshots whose source volume has been deleted but continue to accrue storage charges.
EBS snapshots whose source volume has been deleted are "orphaned" — they no longer back an active volume but continue to accrue storage charges. CostLens flags these snapshots so you can review and delete the ones that are no longer needed.
A snapshot may be the only remaining copy of data
Even though the source volume is gone, the snapshot may still hold data that is referenced by an AMI or needed for a future restore. CostLens does not verify AMI dependencies automatically. Check that no AMI references this snapshot before deleting. Once deleted, the data cannot be recovered through CostLens.
How it works
CostLens lists all snapshots
Lists all EBS snapshots owned by your account using ec2:DescribeSnapshots.
Cross-references against existing volumes
Snapshots whose source volume no longer exists are flagged as orphaned.
Confirmation dialog
When you click Apply Fix, CostLens shows a confirmation dialog explaining the AMI dependency risk and two required acknowledgement checkboxes.
Deletes the snapshot
Once both checkboxes are checked and you confirm, CostLens calls ec2:DeleteSnapshot.
How to check if a snapshot is used by an AMI
- Open EC2 → AMIs in the AWS Console and search for AMIs registered in your account.
- Select each AMI → Block device mappings → check if the Snapshot ID matches.
- If the snapshot backs an AMI you still use, do not delete it — deregister the AMI first if no longer needed.
- If no AMI references the snapshot, it is safe to proceed with deletion.
Severity levels
| Severity | Snapshot storage |
|---|---|
| high | ≥ 100 GB — significant orphaned backup cost |
| medium | 20–100 GB |
| low | <20 GB — minor cleanup opportunity |
Tip
After applying a fix, verify in the AWS Console that no AMIs are in a broken state. Deregister unused AMIs first to avoid issues.