EBS usage types: VolumeUsage.gp3, SnapshotUsage and the rest
EBS:VolumeUsage.gp3 is the usage type for gp3 volume storage, billed in GB-months for the size you provision, whether or not the volume is attached or the disk is full. Related lines bill provisioned IOPS and throughput above the gp3 baseline (EBS:VolumeP-IOPS.gp3, EBS:VolumeP-Throughput.gp3) and snapshot storage (EBS:SnapshotUsage). All appear under EC2 - Other with a Region prefix.
The usage types, decoded
| Usage type | Meter | Unit |
|---|---|---|
EBS:VolumeUsage.gp3 | gp3 storage | GB-Month |
EBS:VolumeUsage.gp2 | gp2 storage (IOPS included) | GB-Month |
EBS:VolumeUsage.io2 / .piops | io2 / io1 storage | GB-Month |
EBS:VolumeUsage.st1 / .sc1 | HDD storage | GB-Month |
EBS:VolumeP-IOPS.gp3 | gp3 IOPS above 3,000 | IOPS-Month |
EBS:VolumeP-Throughput.gp3 | gp3 throughput above 125 MB/s | MB/s-Month |
EBS:VolumeP-IOPS.io2, .io2.tier2, .io2.tier3 | io2 IOPS by tier | IOPS-Month |
EBS:SnapshotUsage | Standard tier snapshots | GB-Month |
EBS:SnapshotArchiveStorage | Archive tier snapshots (full copies) | GB-Month |
EBS:FastSnapshotRestore | Fast snapshot restore, per snapshot per AZ | DSU-Hours |
Prefix examples: EUC1-EBS:VolumeUsage.gp3 is Frankfurt, EU-EBS:SnapshotUsage is Ireland. Storage is metered hourly and billed per second with a 60-second minimum, so a volume that existed for half the month costs half.
Why the line is higher than the data you store
- You pay for provisioned size, not used space. A 1 TiB volume holding 40 GB is billed as 1 TiB.
- Detached volumes still bill. Terminating an instance with Delete on termination off leaves the data volume behind; see unused EBS volumes.
- Stopped instances still bill for every attached volume.
- Provisioned performance on gp3 or io2 bills whether you use the IOPS or not.
- Other Regions and accounts: the prefix gives the Region; in an organisation, group by linked account to find who owns the growth.
- Recycle Bin: deleted volumes held by a retention rule are still billed until the rule releases them.
Find the volumes behind each line
# Volume storage and performance cost by usage type, this month
aws ce get-cost-and-usage --region us-east-1 \
--time-period Start=2026-11-01,End=2026-11-17 \
--granularity MONTHLY --metrics UnblendedCost UsageQuantity \
--filter '{"Dimensions":{"Key":"SERVICE","Values":["EC2 - Other"]}}' \
--group-by Type=DIMENSION,Key=USAGE_TYPE \
--query 'ResultsByTime[0].Groups[?contains(Keys[0], `EBS:`)].[Keys[0],Metrics.UnblendedCost.Amount,Metrics.UsageQuantity.Amount]' \
--output table
# gp3 volumes with IOPS or throughput above baseline
aws ec2 describe-volumes --region eu-west-2 \
--filters Name=volume-type,Values=gp3 \
--query 'Volumes[?Iops>`3000` || Throughput>`125`].[VolumeId,Size,Iops,Throughput,State]' \
--output tableBring each line down
- Delete or snapshot-and-delete unattached volumes (largest and safest win).
- Move gp2 to gp3 for a lower per-GiB price; check IOPS and throughput first (gp2 vs gp3).
- Trim provisioned IOPS and throughput to what
VolumeReadOps,VolumeWriteOpsand throughput metrics show you need, with headroom. - Expire old snapshots and archive long-term ones (EBS snapshot cost).
What not to do: shrink a volume by modifying its size. EBS cannot reduce a volume's size in place; you would need a new, smaller volume and a data copy.
Questions
What is EBS:VolumeUsage.gp3?
The usage type for gp3 volume storage, billed per GB-month for the provisioned size of each volume.
Why am I charged for EBS when my instances are stopped?
EBS bills for provisioned storage until the volume is deleted. Stopping an instance stops instance hours, not volume storage.
What is EBS:VolumeP-IOPS.gp3?
The charge for gp3 IOPS you provision above the 3,000 IOPS baseline included with every gp3 volume.
Storage lines change slowly, which is why nobody looks at them. CloudConsole, a phone app for AWS, shows spend by usage type and explains lines like EBS:VolumeUsage.gp3, so creeping volume costs are easy to check from your phone.
About the app → · Download on the App Store