AWS bill line item
EBS:SnapshotUsage
GB-month charge for EBS snapshots in the Standard tier, billed incrementally on the changed blocks each snapshot stores.
EBS snapshot storage
Verified against official AWS documentation last checked
Why it shows up
Automated backup schedules can accumulate hundreds of snapshots with no expiration, and because snapshots are incremental, each one keeps referencing changed blocks indefinitely until deleted.
The console's per-snapshot size figure overstates what deleting any single snapshot would free, since it's shared incremental data. Teams often mis-estimate cleanup savings as a result.
How to cut it
- Set retention/lifecycle policies to auto-expire old snapshots instead of letting them accumulate.
- Delete snapshots for volumes or instances that no longer exist.
- Consolidate redundant snapshots generated by CI/test pipelines that rebake images frequently.
- Move long-retained, rarely-restored snapshots to a lower-cost archive tier.
How to read a usage type
The colon in EBS:SnapshotUsage doesn't introduce an instance type the way it does in a code like BoxUsage:m5.large. This code carries no region or direction token either, so there's nothing to break down here.
Source
Source: AWS docs →Found EBS:SnapshotUsage on your own bill?
Drop your Cost Explorer CSV into the AWS Bill Analyzer. It'll flag line items like this one on your own bill and link straight back to the fix.
Analyze your own bill →The meter you don't watch still grows.
Waste rarely hides in the service you check every week. CostMon watches every meter on your stack, including the ones you forgot were running.