AWS bill line item
RDS:GP3-Storage
The per-GB-month charge for General Purpose SSD (gp3) storage provisioned on a single-AZ RDS instance, separate from the instance-hour and IOPS/throughput charges.
RDS gp3 storage
Verified against official AWS documentation last checked
Why it shows up
This line scales with allocated storage size, not actual data used. Over-provisioned volumes (sized for future growth that never materialized) keep billing at the full allocated capacity every month.
gp3 storage includes a free baseline of IOPS and throughput, but exceeding that baseline generates separate line items, which is a common source of confusion when a storage bill jumps without a size change.
How to cut it
- Right-size allocated storage to actual usage plus headroom, rather than over-provisioning up front.
- Enable storage autoscaling instead of manually pre-allocating a large volume.
- Check whether provisioned IOPS/throughput above the gp3 baseline are needed before paying for extra performance.
- Periodically audit old snapshots and unattached storage tied to decommissioned instances.
How to read a usage type
The colon in RDS:GP3-Storage 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 RDS:GP3-Storage 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 →A bill read by hand goes stale tomorrow.
Reading one export line by line takes real work. CostMon reads the next one for you, every day, for every provider you connect.