Practical guide
EBS gp3 pricing: separate storage, IOPS, and throughput
calculate EBS gp3 storage and additional IOPS costs. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Capacity and provisioned performance are separate inputs
An EBS gp3 estimate begins with provisioned storage, then adds performance above included baselines where applicable. Used filesystem space is not the same as provisioned volume capacity. A mostly empty volume can still incur its full provisioned storage charge.
The calculator models gp3 storage and additional IOPS in US East. It excludes throughput above the included baseline, snapshots, and other EBS features, so its subtotal is intentionally narrower than the complete volume bill.
Worked example: capacity stays fixed while IOPS changes
Suppose a 500 GB volume is provisioned for 6,000 IOPS. With the calculator’s 3,000 included IOPS baseline, the additional quantity is 3,000 IOPS. The modeled monthly subtotal is 500 × storage rate + 3,000 × additional-IOPS rate.
If provisioning increases to 9,000 IOPS without changing storage, additional IOPS become 6,000. The storage component stays fixed, while the additional-IOPS component doubles. This does not mean the complete volume bill doubles because storage and any omitted components remain separate.
For a proposed reduction to 3,000 IOPS, the additional-IOPS component becomes zero in this model. That is not evidence that the application can operate at that setting; observed latency and I/O demand must support it.
Match units and bottlenecks
IOPS measures operation rate, while throughput measures data volume per second. Large I/O operations can encounter a throughput constraint even when the IOPS count seems modest. The attached instance’s storage capabilities also affect usable performance.
Use monitoring from peak and normal periods before changing provisioning. Record the application impact as well as the price difference. A cost worksheet cannot demonstrate that a database, queue, or build workload has enough performance headroom.
The monthly estimate assumes the stated provisioning persists for the modeled period. A volume created, resized, or removed during the month needs time-aware accounting, and snapshots remain a separate cost review.
Frequently asked questions
Should I enter used disk space? Enter provisioned capacity for the storage charge.
Does the result include all gp3 performance charges? No. Additional throughput is outside this tool’s current subtotal, so include it separately when provisioned.
Calculate your scenario
Use the ebs cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.