EBS snapshots bill per GB month and never delete themselves, so the quiet way a snapshot line grows is simple forgetting: orphaned snapshots from terminated volumes, daily backups with no expiry, and AMIs nobody owns accumulate for years at full price. The fix is lifecycle automation, not manual cleanup: tag every snapshot by owner and purpose, set retention with Amazon Data Lifecycle Manager so copies age out on a schedule, move rarely touched compliance snapshots to the EBS Snapshots Archive tier, and confirm no AMI depends on a snapshot before deleting it. Because snapshots are incremental, the savings are not always obvious from a single snapshot size, which is exactly why this line needs policy rather than spreadsheets.
Here is why snapshot spend creeps, how incremental billing hides it, and a lifecycle policy that stops the bleed.
Why does the snapshot line keep growing?
Three habits drive it. First, backup automation that creates daily or hourly snapshots with no expiry, so a year of dailies sits in storage long after anyone would restore them. Second, orphaned snapshots: when a volume or instance is terminated, its snapshots are not removed, so they linger with no live resource to explain them. Third, AMIs, which are backed by snapshots; deregistering an AMI does not delete its underlying snapshots, so deregistered images leave storage behind. None of these are dramatic on their own, which is why they are forgotten. Multiplied across accounts and years, the snapshot tier becomes one of the largest storage lines on the bill, all of it at the standard per GB month rate that never falls.
How does incremental billing hide the real cost?
EBS snapshots are incremental: only blocks changed since the previous snapshot are stored anew, and unchanged blocks are referenced, not copied. That makes per snapshot size misleading. Deleting a snapshot in the middle of a chain may free almost nothing, because its unique blocks are retained for later snapshots that reference them, and may free a lot if it holds blocks nothing else needs. The practical consequence is that you cannot reason about snapshot savings one snapshot at a time. You reason about retention windows and chains: shortening how long a series is kept, or archiving an entire chain, is what actually reduces stored GB. This is why automation that manages whole lifecycles beats manual deletion of individual snapshots.
What does a sane snapshot lifecycle look like?
| Snapshot class | Retention | Where it lives |
|---|---|---|
| Recreatable data, dev and test | Days, or none | Standard tier, short lifecycle policy |
| Production operational backups | Weeks, tiered daily, weekly, monthly | Standard tier, Data Lifecycle Manager |
| Compliance and long retention | Months to years, rarely restored | EBS Snapshots Archive tier |
| Orphaned and unowned | Delete after verification | Removed once no AMI depends on them |
Drive retention with Amazon Data Lifecycle Manager policies keyed off tags, so the rule applies automatically as new snapshots are created. Archive thresholds and tier pricing are indicative; verify against current AWS pricing.
A worked example
A Fortune 500 retailer found its EBS snapshot line had grown to a meaningful share of total storage with no owner able to explain it. An audit showed roughly half the stored GB came from orphaned snapshots of long terminated volumes and from a backup job that had created dailies with no expiry for over two years. We tagged and aged out the recreatable and orphaned snapshots through Data Lifecycle Manager, moved the genuine compliance copies to the Archive tier, and set tiered retention on production backups. Stored snapshot GB fell sharply and stayed down because the policy now enforces it, contributing to a wider storage program that cut the retailer's storage spend without weakening recovery. Figures are verified against billing data and anonymised.
Frequently asked questions
How are EBS snapshots billed?
Do EBS snapshots get cheaper over time?
How do you safely delete old EBS snapshots?
Stop paying to store what you forgot
We audit EBS snapshot and storage estates and put lifecycle policy in place so waste cannot reaccumulate, as an independent advisory that takes zero provider commissions and answers only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the cloud cost optimization playbook, read the deeper AWS cost optimization guide, and pair it with EBS volume rightsizing and gp3 migration.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.