AWS bill line item
EBS:VolumeUsage.gp2
Billing for the provisioned capacity (GB-month) of General Purpose SSD EBS volumes: gp2 or its newer, usually cheaper sibling gp3.
EBS General Purpose SSD storage (gp2/gp3)
Verified against official AWS documentation last checked
Why it shows up
Every attached (and every unattached, un-deleted) gp2/gp3 volume bills continuously by provisioned size, not by data used, so oversized volumes or orphaned volumes left behind by terminated instances keep charging.
gp2 is being phased out in favor of gp3, which is typically priced lower per GB and decouples performance from capacity, so heavy gp2 usage here usually flags an easy migration win.
How to cut it
- Right-size volumes against actual usage instead of provisioning "just in case."
- Migrate gp2 volumes to gp3 for the per-GB savings.
- Find and delete unattached volumes left behind by terminated instances.
- Automate snapshot-and-delete for stale dev/test volumes instead of doing it manually.
How to read a usage type
The colon in EBS:VolumeUsage.gp2 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:VolumeUsage.gp2 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.