Skip to content
Calcrivo

EC2 AMI Storage Calculator

Cost AMI generations as incremental EBS snapshots across regions and see how much block-level dedupe saves.

Inputs

GB

Snapshots store written blocks, not the provisioned volume size.

%
images
regions

A cross-region copy starts a fresh full snapshot in the destination region.

USD/GB

Editable — standard EBS snapshot storage is about $0.05 per GB-month.

Monthly Snapshot Cost

$7.47

Billable Snapshot Storage

149.4GB

Billable Storage in Bytes

139.14 GiB

Saved by Incremental Storage

930.6GB

Effective Dedupe Ratio

7.23x

Annual Snapshot Cost

$89.64

Step by step

  1. Values used

    Used data in the first image = 30 GB; Blocks changed between builds = 6 %; Image generations retained = 12 images; Regions the image is copied to = 3 regions; Snapshot price per GB-month = 0.0500 USD/GB

  2. EC2 AMI Storage

    billable GB per region = first image GB + (generations − 1) × changed GB; total = that × regions.

  3. Monthly Snapshot Cost

    = 7.47

  4. Billable Snapshot Storage

    = 149.4 GB

  5. Billable Storage in Bytes

    = 149,400,000,000.00

  6. Saved by Incremental Storage

    = 930.6 GB

  7. Effective Dedupe Ratio

    = 7.23 x

  8. Annual Snapshot Cost

    = 89.64

How it works

EBS snapshots are incremental at block level within a region, so the second and later generations of an AMI only bill for blocks that actually changed — a 30 GB image rebuilt weekly with 6% churn costs far less than 12 full copies. Cross-region copies break the chain: the first copy into each region is a full baseline, which is why the region count multiplies the whole figure rather than adding a delta. Retention is nearly free while churn is low and expensive the moment a build rewrites most of the filesystem, so the change rate — not the generation count — is the lever that decides whether an image pipeline is cheap.

Formula

EC2 AMI Storage

billable GB per region = first image GB + (generations − 1) × changed GB; total = that × regions.

delta
Blocks rewritten between builds, the only new data stored
generations
Images kept by your lifecycle policy
regions
Each destination region starts its own full baseline

Frequently Asked Questions

How is EC2 AMI Storage calculated?

billable GB per region = first image GB + (generations − 1) × changed GB; total = that × regions. EBS snapshots are incremental at block level within a region, so the second and later generations of an AMI only bill for blocks that actually changed — a 30 GB image rebuilt weekly with 6% churn costs far less than 12 full copies. Cross-region copies break the chain: the first copy into each region is a full baseline, which is why the region count multiplies the whole figure rather than adding a delta.

Why does EC2 AMI Storage matter?

Retention is nearly free while churn is low and expensive the moment a build rewrites most of the filesystem, so the change rate — not the generation count — is the lever that decides whether an image pipeline is cheap.

What values do I need to enter?

This calculator takes 5 inputs: Used data in the first image, Blocks changed between builds, Image generations retained, Regions the image is copied to, Snapshot price per GB-month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Does deregistering an AMI delete the storage?

No. Deregistering removes the image but leaves the backing snapshots, which keep billing. Lifecycle policies must delete the snapshots as well, and this is one of the most common sources of quiet, long-lived EBS spend.

You might also need