One Volume, Three Bills

An EBS volume is storage, IOPS and throughput sold at three rates that never convert into each other. The two performance meters include a per-volume baseline, and that word volume is the whole story

Published: 2026-11-16  |  jslet Research  |  13 min read

๐Ÿ“‘ In This Briefing

A 2,000 GiB gp3 volume in us-east-1, provisioned to its documented ceilings of 80,000 IOPS and 2,000 MiB/s, bills $620.00 a month. The console shows one volume. The invoice shows one line. Neither of them shows the $620 split, so almost nobody learns that $460 of it buys nothing you can put a file on.

Open the price list and there is no per-volume price at all, and no $620. There are three rates. Storage is $0.08 per GiB-month. Provisioned IOPS above the included baseline is $0.005 per IOPS-month. Provisioned throughput above the included baseline is $0.04 per MiB/s-month, quoted by AWS as $40.96 per GiBps-month. Multiply each by the quantity you configured and add.

2,000 GiB × $0.08 = $160.00
77,000 IOPS × $0.005 = $385.00
1,875 MiB/s × $0.04 = $75.00
total = $620.00

The first line is about bytes. The second and third are about a rate at which bytes can be touched, charged as a monthly subscription to a number. Storage is a quarter of the bill, and the three quarters above it are the part that changes when a workload gets busier without getting larger.

1. Three Meters, Three Units

The awkwardness starts with the units. A GiB-month is a quantity of bytes held for a month. An IOPS-month is an operation rate sustained for a month. A MiB/s-month is a rate of a rate, a bandwidth held open whether or not anything crosses it. Nothing in the invoice converts between them, and they are added together only because they share a currency.

Meter Unit billed Rate Included free Ceiling per volume
StorageGiB-month$0.080noneno limit
Provisioned IOPSIOPS-month$0.0053,000 IOPS$385.00
Provisioned throughputMiB/s-month$0.040125 MiB/s$75.00

The last column is worth reading before the rest of the article. Two of the three meters have hard ceilings, and they are small: no gp3 volume can ever be billed more than $385.00 for IOPS or $75.00 for throughput, because 80,000 and 2,000 are the documented maxima. Only storage is unbounded. So the shape of a large bill is decided by one question: how many bytes did you accumulate. The performance lines are capped, and on a big enough volume they become rounding errors.

Three meters, three rates, one currency, and no exchange rate between them. That is why an invoice can grow forty percent in a month while the data on disk grew four.

2. The Baseline Is Per Volume, Not Per Gigabyte

Two of the three meters do not start at zero. Every gp3 volume includes 3,000 IOPS and 125 MiB/s at no charge, at any size, and the word that matters is every. The allowance is granted per volume. It is not a rate per gigabyte that accumulates as the volume grows, and it does not scale with anything except the number of volumes you own.

Price the allowance from the rate card, because that is the only published price for these quantities. 3,000 IOPS at $0.005 is $15.00 a month. 125 MiB/s at $0.04 is $5.00. The free allowance is worth $20.00 a month per volume, and the cheapest volume that carries it is 1 GiB, which costs $0.08.

Volume size Storage bill Baseline value Performance ÷ storage Free IOPS per GiB
1 GiB$0.08$20.00250×3,000
100 GiB$8.00$20.002.5×30
1,000 GiB$80.00$20.000.25×3
16,000 GiB$1,280.00$20.000.016×0.19

Read the first and last rows together. On a 1 GiB volume the free performance is worth two hundred and fifty times the storage; on a 16 TiB volume it is 1.6 percent of it. That two-hundred-and-fifty-fold spread is not a pricing error, and it is the reason two teams with the same total capacity can have wildly different bills.

One honest caveat: the $20.00 is a notional value, not a line item. AWS does not credit it, itemise it, or let you sell it back. It is what those quantities cost when you buy them above the baseline, which is the only price the service publishes for them, and it is the right number to use when deciding whether a second volume is worth its own $0.08.

3. What 1,000 IOPS Actually Costs

The rate card says $5.00. The rate card is quoting the first meter only. Above the 125 MiB/s baseline, the throughput a given IOPS count implies is a second purchase, and how much of it you need depends entirely on your average I/O size.

A thousand IOPS at 4 KiB moves 3.906 MiB/s. At 128 KiB it moves 125 MiB/s. Same thousand IOPS, thirty-two times the bytes, and the throughput meter charges for the difference.

Average I/O Bandwidth per 1,000 IOPS Throughput charge True cost of 1,000 IOPS
4 KiB3.91 MiB/s$0.16$5.16
8 KiB7.81 MiB/s$0.31$5.31
16 KiB15.63 MiB/s$0.63$5.63
25.6 KiB25.00 MiB/s$1.00$6.00
32 KiB31.25 MiB/s$1.25$6.25
64 KiB62.50 MiB/s$2.50$7.50
128 KiB125.00 MiB/s$5.00$10.00
256 KiB250.00 MiB/s$10.00$15.00

There is no cliff here, only a ramp. The same thousand IOPS costs three times as much at 256 KiB as at 4 KiB, and every dollar of the difference is the throughput meter charging for bytes the IOPS already imply. A random-read database and a log shipper can provision the same IOPS count and pay the same IOPS bill while owing completely different throughput bills, because one of them reads 4 KiB and the other reads a quarter of a megabyte.

Two limits keep this table honest. The throughput meter saturates at $75.00, so above 8,000 IOPS at 256 KiB the marginal IOPS cost falls back to $5.00, because 2,000 MiB/s cannot carry more. And these are marginal rates above the baseline, so the first 3,000 IOPS and the first 125 MiB/s are already paid for by the storage line.

4. The 500 IOPS-per-GiB Floor

gp3 will not sell more than 500 IOPS per GiB of volume, which is a bundling rule wearing a performance limit's clothes. It says: fast, small disks are not on the menu. To reach a given IOPS count you must own enough bytes to carry it.

Provisioned IOPSMinimum volumeStorage billIOPS billTotalPer GiB-month
8,00016 GiB$1.28$25.00$26.28$1.64
16,00032 GiB$2.56$65.00$67.56$2.11
80,000160 GiB$12.80$385.00$397.80$2.49

The last column is the one to remember. A 32 GiB volume at 16,000 IOPS costs $2.11 per GiB-month, twenty-six times the $0.08 headline rate. The headline is a floor price for a volume that buys no performance at all, and it is quoted as though that were the normal case.

The ratio has a second consequence that cuts the other way. Below 6 GiB, 500 IOPS per GiB would permit fewer than the 3,000 IOPS the volume already has for free, which is a clean demonstration that the baseline sits outside the ratio rather than inside it. A 1 GiB volume is documented to deliver 3,000 IOPS, six times the ratio enforced everywhere else, and it costs eight cents.

5. Volume Count Is a Price Lever

Put the two previous sections together and a lever appears that nobody puts in a design review. Suppose the fleet needs 2,000 GiB and 60,000 IOPS.

One 2,000 GiB volume. Storage is $160.00. The baseline covers 3,000 IOPS, so 57,000 must be provisioned at $0.005, which is $285.00. Total $445.00.

Twenty volumes of 100 GiB. Storage is twenty times $8.00, which is still $160.00. Each volume carries 3,000 IOPS of baseline, so the fleet has 60,000 IOPS without provisioning a single one. Total $160.00.

ShapeStorageIOPS billTotal / monthPer year
1 × 2,000 GiB at 60,000 IOPS$160.00$285.00$445.00$5,340.00
20 × 100 GiB at baseline$160.00$0.00$160.00$1,920.00

The difference is $285.00 a month and $3,420.00 a year, and it equals the IOPS line to the cent. That is the point: nothing is being discounted. The same quantity has moved from a metered column into an unmetered one, and the invoice cannot tell the difference between a volume that earned its baseline and one that did not.

The throughput side of the same fleet is more interesting than the arithmetic suggests. Twenty volumes carry twenty baselines, so 2,500 MiB/s aggregate, which is more than any single gp3 volume can be provisioned to, because 2,000 MiB/s is the per-volume ceiling. This is not a cheaper way to buy the same product; it is a product the single volume cannot sell at any price.

6. Where the Lever Stops

Four things cap the trick, and three of them are not financial.

A filesystem lives on one volume. Twenty volumes deliver 60,000 IOPS to a filesystem only if they are striped with LVM or RAID 0, or if the application writes to twenty separate paths. Kafka log directories, Cassandra data directories and object-store shards do the latter naturally. A single Postgres data directory does not, and striping it means one lost volume takes the whole fileset with it, which is a bad trade for primary data and a reasonable one for replicas, caches and scratch space.

Attachment limits. Nitro instances support up to 28 EBS attachments, fewer on smaller types. Twenty-eight is a real ceiling on how many baselines one instance can harvest, and it is reached well before the arithmetic runs out.

Paid IOPS converge. Above each volume's baseline, IOPS costs $0.005 wherever it sits. Splitting does not make paid IOPS cheaper: the twentieth volume's 3,001st IOPS costs exactly what the first volume's 3,001st did. The lever harvests free baseline and nothing else.

The baseline has to be usable. Twenty volumes each running at 200 IOPS is $160 a month spent to acquire 60,000 IOPS of headroom that four of them could have used. Splitting is a bet that the workload will spread; if it concentrates on one shard, the geometry has bought a ceiling nobody reaches.

Splitting a volume is not a discount. It is a decision about which column of the invoice your performance lands in, and it only works while the performance still fits inside a free allowance.

7. How Many Meters a Volume Has

None of this vocabulary existed for gp2, and the contrast explains why the three meters look strange. The three SSD families on the same service are billed through three different numbers of meters, and the count is a design decision rather than a property of the hardware.

Volume typeMetersStorageIOPSThroughput
gp21$0.10 / GiBbundled, 3 per GiBderived from I/O size
gp33$0.08 / GiB$0.005 above 3,000$0.04 above 125 MiB/s
io22$0.125 / GiB$0.065 per IOPSfolded into IOPS

gp2 sells IOPS as a fraction of capacity. At 3 IOPS per GiB, the only way to buy IOPS is to buy bytes you do not need. Sixteen thousand IOPS requires 5,334 GiB, which costs $533.40 a month. The same 16,000 IOPS on gp3 requires a 32 GiB volume for the ratio and 13,000 paid IOPS, which is $67.56.

For 16,000 IOPSVolume neededStorageIOPS meterTotal
gp2, 3 IOPS per GiB5,334 GiB$533.40included$533.40
gp3, 500 IOPS per GiB32 GiB$2.56$65.00$67.56

The 7.9× gap is not a discount on storage and not a promotional rate. It is the price of unbundling: gp2 forced 5,302 GiB of capacity into a purchase that was only ever about speed, and gp3 sells the speed on its own meter. The three bills exist because the bundling was hiding a number much larger than the storage rate suggested.

io2 goes the other way and folds the third meter into the second. It bills storage at $0.125 per GiB-month and IOPS at $0.065, tiered to $0.0455 above 32,000 and $0.03185 above 64,000, and it has no throughput line at all. Throughput is capped at 256 KiB/s per provisioned IOPS, so the bandwidth is not free; it is pre-purchased inside a rate thirteen times gp3's. At 16,000 IOPS on 500 GiB, io2 bills $62.50 of storage and $1,040.00 of IOPS, or $1,102.50.

Set that against the gp3 equivalent for the same 16,000 IOPS and the same 1,000 MiB/s ceiling. The gp3 volume is 32 GiB at $2.56, plus $65.00 of IOPS, plus $35.00 to lift throughput from 125 to 1,000 MiB/s, for $102.56. The gap is 10.7×, and per unit of bandwidth it is starker still: io2's $0.065 per IOPS buys 0.25 MiB/s, which is $0.26 per MiB/s-month against gp3's $0.04, a factor of 6.5.

Bundling hides the bandwidth price inside the storage rate. Unbundling reveals it. Folding it into a thirteenfold IOPS rate hides it again, in plain sight, on a line item nobody divides.

Which is the honest case for io2? Not bandwidth and not IOPS per dollar. It is the two things the table cannot show: 99.999 percent annual durability against gp3's 99.8 to 99.9, and sub-millisecond latency against single-digit milliseconds. A workload that can replay from a log does not need the first. A workload that holds the only copy of something, or that needs the second, is not shopping on this table.

8. The Mix Shifts With Size

Hold the workload still and vary only the size. Sixteen thousand IOPS, 4 KiB average I/O, so 62.5 MiB/s and no throughput charge at any of these sizes.

VolumeStorageIOPSTotalStorage share
32 GiB$2.56$65.00$67.563.8%
100 GiB$8.00$65.00$73.0011.0%
500 GiB$40.00$65.00$105.0038.1%
2,000 GiB$160.00$65.00$225.0071.1%

The bill more than triples across the table and the performance line never moves. That is the correct mental model for the three meters: performance is a fixed subscription, storage is the variable. A team that provisioned for a 32 GiB working set and later grew the volume to 2,000 GiB has increased its bill by 233 percent without changing a single performance parameter, and the invoice will not say so.

Turn the table around and it makes a different point. $225 a month buys either 2,000 GiB of capacity running at baseline speed, or 16,000 IOPS on a 32 GiB volume with 190 GiB of storage left over. One invoice total, two entirely different products, and no way to tell from the total which one you bought.

9. The Fourth Meter

There is a fourth bill attached to the same volume, and it is the only one with no performance component at all. Snapshots are billed at $0.05 per GiB-month in the standard tier and $0.0125 in archive, on the blocks actually stored rather than on the size of the volume. No baseline, no size ratio, no IOPS, no throughput.

That makes the snapshot bill the easiest of the four to reason about and the easiest to let grow: 400 GiB of data changing at 2 percent a day with thirty days of retention stores about 632 GiB, which is $31.60 a month, and the first snapshot alone accounts for $20.00 of it. The arithmetic is in EBS Snapshot Cost; what matters here is that it is a fifth line on an invoice that already has three, and that none of the three EBS metering rules above apply to it.

10. Reading Your Own Bill

Three checks, in order of usefulness.

Effective rate per GiB-month. Divide the monthly EBS bill for a volume by its size. A gp3 volume buying no performance lands at exactly $0.08. Anything above that is provisioned IOPS, provisioned throughput, or both, and the excess divided by $0.005 and $0.04 recovers how much of each. This one division separates a storage problem from a performance problem, and it takes ten seconds per volume.

Provisioned IOPS per GiB across the fleet. Above 30 means the baseline is doing real work and the split question is worth asking. Below 3 means you are buying capacity and the IOPS column should read zero. The number also tells you whether the fleet is shaped for throughput or for random access, because a fleet at 0.19 IOPS per GiB is a fleet of big slow volumes and one at 500 is a fleet of small fast ones.

The average I/O size. Divide total throughput by total IOPS. That single quotient decides whether the throughput meter or the IOPS meter is the one to optimise, and it is already printed in every iostat line as rkB/s + wkB/s over r/s + w/s. The volume-level version of the same analysis is in The 0.25 Rule.

Cost and Usage Report data splits all of this into separate usage types already, one each for volume storage, provisioned IOPS and provisioned throughput, which is the cheapest possible way to see which meter moved. If the report is not on, the division above gets you the same answer from the invoice total.

11. Frequently Asked Questions

Why does a 500 GiB volume at 16,000 IOPS cost $105 when the price is $0.08 per GiB?

Because only one of the three meters is storage. 500 GiB at $0.08 is $40.00. IOPS above the 3,000 baseline is 13,000 units at $0.005, which is $65.00. Throughput at a normal block size never leaves the 125 MiB/s baseline, so that meter reads zero. The total is $105.00, and 62 percent of it buys a number that does not appear on any disk.

If I provision more IOPS, do I get more throughput for free?

No. Throughput is separately provisioned, and raising IOPS does not raise it. The 0.25 MiB/s per provisioned IOPS figure is an upper bound on throughput given your IOPS, not an entitlement to it. A volume at 80,000 IOPS with throughput left at baseline still delivers 125 MiB/s. This is the most common surprise on a first gp3 bill: the IOPS was bought and the bandwidth was assumed.

Is splitting one big volume into many small ones actually cheaper?

For the baseline, yes, and only for the baseline. Each volume carries 3,000 IOPS and 125 MiB/s at any size, so 2,000 GiB split twenty ways carries 60,000 IOPS for $160 where one volume needs $285 of paid IOPS to reach the same count. Nothing is discounted: the saving is the IOPS line that stops being metered. Past the baseline, splitting saves nothing, because paid IOPS costs $0.005 per unit wherever it sits.

Why is gp2 more expensive than gp3 for the same IOPS?

Because gp2 sells IOPS as a fraction of capacity rather than on its own meter. At 3 IOPS per GiB, buying 16,000 IOPS means buying 5,334 GiB at $0.10, which is $533.40. gp3 separates the meters: 32 GiB satisfies the 500 IOPS-per-GiB ratio, and 13,000 paid IOPS adds $65.00, for $67.56. The 7.9× gap is the cost of the bundling, not a discount on gp3.

Does the 500 IOPS-per-GiB limit apply to the 3,000 IOPS baseline?

No. The ratio governs IOPS provisioned above the baseline, and the baseline is granted per volume without reference to size. That is why a 1 GiB volume is documented to deliver 3,000 IOPS, six times the ratio the service enforces everywhere else. Below 6 GiB the ratio would permit less than the volume already has for free, which is the clearest sign that the baseline sits outside it.

Are snapshots part of these three meters?

No. Snapshots are a fourth meter with no performance component: $0.05 per GiB-month standard and $0.0125 archive, billed on blocks stored rather than on volume size. There is no baseline and no size ratio, so a snapshot bill depends on how many versions you keep and how much of the volume changes per day.

How do I tell which meter grew last month?

Divide the monthly bill by the volume's GiB-month. A volume buying no performance lands at exactly $0.08. The excess above that, divided by $0.005 and $0.04, recovers the two performance quantities. Cost and Usage Report data splits the same three components into separate usage types if the report is enabled.

12. Methodology & Disclosure

Every rate and every ceiling in this article was read from the AWS price list feed and the EBS volume-type documentation for us-east-1 on 2026-11-16. Every derived figure is arithmetic on those inputs and is reproducible with a calculator; none of it comes from a benchmark, a support case, or a vendor estimate.

Pricing Basis, Sources & Assumptions

Pricing inputBasis used in this article
SourceAmazon EBS pricing for the volume-type definitions and billing rules, cross-checked against the AWS price list feed for EBS. The three gp3 rates used throughout are $0.08 per GiB-month, $0.005 per provisioned IOPS-month, and $40.96 per GiBps-month of provisioned throughput, which is $0.04 per MiB/s-month. gp2 is $0.10 per GiB-month. Snapshots are $0.05 per GiB-month standard and $0.0125 archive.
RegionUS East (N. Virginia), us-east-1. Every other region is priced at or above these rates and the difference is not modelled here.
CurrencyUSD. List price, tax excluded, no negotiated discount, savings plan, reserved capacity or credit applied.
Last checked. The three gp3 rates, the gp2 rate, both snapshot rates, the 3,000 IOPS and 125 MiB/s baseline, the 80,000 IOPS and 2,000 MiB/s ceilings, and the 500 IOPS-per-GiB ratio were re-read on this date from the gp3 volume type documentation and the price feed.
AssumptionsVolumes are billed for a full 730-hour month. The $20.00 baseline valuation prices the free allowance at the marginal rates above it, which is a notional figure rather than a credit; AWS neither itemises nor refunds it. Throughput charges assume average I/O size, not a distribution, so a bimodal workload will see a bill that matches neither row of the table. gp2 throughput is derived from its documented formula rather than measured. Instance-level limits such as the 28-attachment ceiling vary by instance type, and no instance type is assumed anywhere in the arithmetic.

What this article is not. It is not a benchmark and not a recommendation to split anything. Striping changes the failure domain, and a saving that costs you a fileset is not a saving. It also does not model io2, st1 or sc1, which have different meter structures; the comparison across those types is in EBS Volume Cost. Verify the two ratios on your own volumes before changing a shape, because both are vendor-documented values that have been revised before.

Independence. No vendor sponsorship and no affiliate links. No cloud provider was contacted, and none supplied data for this briefing.

References & Further Reading

  1. AWS. Amazon EBS General Purpose SSD volumes — gp3's 3,000 IOPS and 125 MiB/s baseline, 80,000 IOPS and 2,000 MiB/s maxima, the 500 IOPS-per-GiB and 0.25 MiB/s-per-IOPS ratios, and the statement that maximum throughput requires 8,000 IOPS or more. docs.aws.amazon.com/ebs/latest/userguide/general-purpose.html
  2. AWS. Amazon EBS pricing — the three gp3 meters, the gp2 single meter, and the snapshot tiers. aws.amazon.com/ebs/pricing
  3. AWS. Amazon EBS volume types — the gp2 3 IOPS-per-GiB scaling rule, the 16,000 IOPS ceiling at 5,334 GiB, the 128 to 250 MiB/s range, and the dagger footnote on required I/O size. docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html
  4. AWS. Amazon EBS snapshots — incremental block storage, the standard and archive tiers, and the 90-day minimum retention in archive. docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html
  5. Related: EBS Volume Cost Calculator · EBS Snapshot Cost Calculator · The 0.25 Rule · IOPS to Throughput Estimator · Cloud Storage Cost · DynamoDB Capacity Cost · Methodology

๐Ÿ“œ Copyright & Attribution

© 2026 jslet Research. This article is an original work published on jslet (jslet.com). All rights reserved.

Sharing & Reprinting: You may share excerpts (up to 200 words) with a mandatory, do-follow link back to the original article URL. Full reproduction, translation, or adaptation requires prior written permission. Contact: support@jslet.com.

Model Disclaimer: Rates and ceilings are vendor-published list values for us-east-1 and change without notice. Provisioned performance is a target, not a guarantee. Striping volumes changes the failure domain and should not be adopted on the strength of a cost model alone.