🗄️ EBS Snapshot Cost

Snapshot storage is the one EBS meter that has nothing to do with what you provisioned. It counts blocks that have been written and are still referenced by a retained snapshot, so the bill is set by two numbers an infrastructure diagram never shows: how long you keep snapshots, and how much of the data changes between them. A volume that churns two percent a day and keeps thirty days of history carries half again its own data in snapshots. The same volume kept for ninety days carries 2.8 times.

📐 Backup Policy

Change rate is the share of live data rewritten between two snapshots. A database writing its whole working set daily is 100%; a static file server is near zero. Use the sustained figure over the retention window, not a peak.

Restores matter only on the archive tier, where each one costs $0.03 per GB of snapshot retrieved. On the standard tier the field is ignored, because a standard snapshot can be restored at no retrieval charge.

The first snapshot is the expensive one

An EBS snapshot copies the blocks that have been written, not the space that was provisioned. A 1,000 GiB volume holding 400 GiB of data produces a first snapshot of about 400 GiB, and the 600 GiB of never-written space costs nothing — snapshots do not save empty blocks. Every snapshot after that stores only the blocks that changed since the previous one, so the marginal price collapses immediately and then stays low.

retained = snapshots per day × retention days stored = data in use × (1 + (retained − 1) × daily change) standard = stored × $0.05 per GiB-month archive = stored × $0.0125 per GiB-month, 90-day floor retrieval = restored GB × $0.03 (archive only) 400 GiB, 2%/day, 30 daily snapshots stored = 400 × (1 + 29 × 0.02) = 632 GiB standard = 632 × $0.05 = $31.60 / month

Thirty snapshots of a 400 GiB dataset cost $31.60 a month, and the first one alone would have cost $20.00. That is the shape of the whole problem: the twenty-nine extra copies added $11.60, so the policy is cheap and the first copy is the expensive part. Which means the question worth asking is not "how many snapshots" but "how much data am I keeping that I no longer need".

Retention and churn set the bill, size does not

Doubling retention almost doubles the incremental term, and doubling the change rate does the same. Doubling the volume size does nothing at all unless the extra space is actually written to. This is the inverse of how people usually reason about backup cost, and it is why a 4 TiB volume holding 200 GiB of cold archives is cheaper to protect than a 500 GiB database that rewrites itself daily.

Policy on 400 GiB of dataSnapshotsStoredStandard / month
7 days, 1%/day7424 GiB$21.20
30 days, 1%/day30516 GiB$25.80
30 days, 2%/day30632 GiB$31.60
30 days, 5%/day30980 GiB$49.00
90 days, 2%/day901,112 GiB$55.60
90 days, 5%/day902,180 GiB$109.00
24 snapshots/day, 30 days, 2%/day7206,152 GiB$307.60

The last row is the one that surprises people. Taking a snapshot every hour instead of every day multiplies the retained copies by twenty-four and the bill by roughly ten, because the increments are smaller but there are twenty-four times as many of them. Hourly retention over a week is a reasonable policy. Hourly retention over a month is how a $30 backup line becomes a $300 one.

Snapshot storage is 62.5% of the price of live storage per gigabyte. Retaining one full extra copy of a dataset costs $0.05 where the gp3 volume holding it costs $0.08 — the backup is not free, and it is not cheap.

Deleting a snapshot usually frees nothing

Snapshots are a chain, not a set of independent files. Each new snapshot references blocks written by earlier ones and adds only what changed, so a block that first appeared in Tuesday's snapshot stays on the bill as long as any later snapshot still points at it. Deleting Tuesday's snapshot while Thursday's exists releases the reference but not the bytes.

The practical consequence is that pruning a chain from the middle is a no-op on the invoice, and pruning it from the front frees only the blocks that no surviving snapshot still needs. To actually reclaim storage you delete the entire chain for a volume, which is why retention policies that expire snapshots one at a time appear not to work. The bill does step down eventually, as the last snapshot referencing a given generation of blocks expires, but the step is proportional to the age of the data, not to the snapshot you deleted.

The same independence cuts the other way when a volume is decommissioned. Snapshots live in S3 and have no dependency on the source volume, so destroying the instance and the volume leaves the backups billing indefinitely. Orphaned snapshot chains are one of the few EBS charges that can run for years with no running resource to explain them, and they are invisible in any view that groups cost by instance.

Archive is four times cheaper with a 90-day floor

EBS Snapshots Archive stores a full copy of a snapshot at $0.0125 per GiB-month, a quarter of the standard rate. It is a genuinely different product rather than a discount tier, and three of its properties decide whether it saves money.

PropertyStandardArchive
Storage$0.05 / GiB-month$0.0125 / GiB-month
Minimum retentionNone90 days, billed even if deleted early
Retrieval fee$0.00$0.03 / GB
Restore timeImmediateMinutes to hours
Restored copy—Billed at $0.05 while restored; archive copy keeps billing
Typical restore window—1 to 5 days, then re-archived

The 90-day floor turns storage into a minimum commitment: archiving a 400 GiB snapshot and deleting it the next morning still bills 90 days at $0.0125, or $15.00 — the same as 22.5 days of leaving it in the standard tier. Delete it at day 70 and the remaining 20 days are charged anyway.

Retrieval is the sharper edge. The saving is $0.0375 per GiB-month, and one restore costs $0.03 per GB, so a snapshot must sit archived for 24 days before a single restore has paid for itself. Restore the same archive twice a quarter and the standard tier was cheaper all along, before the restore window is even counted. Archive is for the copy you are keeping for a compliance auditor, not for the copy you might need on Tuesday.

What the model assumes, and where it bends

The formula multiplies the change rate by the retained snapshot count, which treats each snapshot as storing a fresh copy of every changed block. That is right for append-heavy workloads and for filesystems that allocate copy-on-write, where an overwritten block becomes a new block and the old one survives. It overstates the bill when a workload rewrites the same blocks in place, because the second and third versions of a block still occupy one slot in the chain.

The error is bounded and worth understanding rather than eliminating. The lower bound is the size of the live data, since the first snapshot already contains every written block. The upper bound is the total bytes written since the chain began, which for a heavy writer can be several times the dataset. Real workloads land between the two, and a figure derived from this page should be read as the shape of the bill rather than a quote.

What is not modelled, and belongs in any real estimate: incremental snapshot copies to another region, which bill data transfer plus destination storage and are priced separately; Fast Snapshot Restore at $0.75 per DSU-hour, charged for as long as the feature is enabled rather than per restore; EBS direct API request charges for block-level backup tools; and the 30 GiB of free snapshot storage per account, which is not subtracted for the same reason as everywhere else on this site.

The cheapest change to most backup bills is not a tier and not a tool. It is asking which of the retained snapshots would ever be restored, and deleting the chain behind the answer.

Pricing Basis, Sources & Assumptions

Every rate on this page is a published vendor list price — no negotiated discounts, private pricing, savings plans, credits or enterprise agreements. Totals are in USD and exclude tax. Rates were last checked against the sources below on .

Pricing inputBasis used on this page
SourceAmazon EBS pricing for the snapshot billing rules, the 90-day archive minimum, the early-delete charge and the temporary-restore behaviour, cross-checked against the AWS price list feed for EBS for the exact us-east-1 rates: $0.05 per GiB-month for standard snapshot storage, $0.0125 per GiB-month for archive storage and $0.03 per GB for archive retrieval.
RegionUS East (N. Virginia), us-east-1. Other regions are priced higher and the difference is not modelled here.
CurrencyUSD — list price, tax excluded
Last checked — all three snapshot rates plus the 90-day minimum were re-read from both sources on this date.

Modelling assumptions