S3 GET Request Cost Calculator
Work out S3 GET request and egress cost after a CDN absorbs most reads, and see which of the two dominates.
About S3 GET Request Cost Calculator
Only the cache misses reach the bucket, so the cache hit ratio scales both the request count and the bytes leaving S3. Because a GET costs about 0.0004 USD per thousand while a GB of egress costs cents, transfer almost always dominates once objects are more than a few KB. Both rates are user-supplied list prices — check the current figures on the AWS S3 and data transfer pricing pages for your region. It shows that raising a cache hit ratio from 88% to 95% halves the origin bill, which is usually a cheaper lever than any storage-class change.
Formula
S3 GET Request Cost
origin requests = viewer requests x (1 − hit ratio); cost = origin requests ÷ 1000 x GET price + origin requests x object size x egress price.
- hit ratio
- Share of viewer requests served from CDN cache
- object size
- Average bytes returned per request
Worked example
With the default values below, S3 GET Request Cost Calculator returns Monthly Read Cost of $95.10. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Viewer requests per monthminimum 0 requests
- 50,000,000 requests
- CDN cache hit ratioaccepts 0–100 %
- 88 %
- Average object sizeminimum 0 KB
- 180 KB
- GET and SELECT priceminimum 0 USD per 1,000 requests
- 0.0004 USD per 1,000 requests
- Data transfer out to the internetminimum 0 USD per GB
- 0.09 USD per GB
Results
- Monthly Read Cost
- $95.10
- Requests Reaching S3
- 6,000,000
- GET Request Cost
- $2.40
- Data Transferred Out
- 1,029.97 GB
- Data Transfer Cost
- $92.70
Step by step
- 1Values used
- 2S3 GET Request Cost
- 3Monthly Read Cost= 95.10
- 4Requests Reaching S3= 6,000,000
- 5GET Request Cost= 2.40
- 6Data Transferred Out= 1,029.97 GB
- 7Data Transfer Cost= 92.70
Assumptions and limits
- The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is S3 GET Request Cost calculated?
origin requests = viewer requests x (1 − hit ratio); cost = origin requests ÷ 1000 x GET price + origin requests x object size x egress price. Only the cache misses reach the bucket, so the cache hit ratio scales both the request count and the bytes leaving S3. Because a GET costs about 0.0004 USD per thousand while a GB of egress costs cents, transfer almost always dominates once objects are more than a few KB. Both rates are user-supplied list prices — check the current figures on the AWS S3 and data transfer pricing pages for your region.
Why does S3 GET Request Cost matter?
It shows that raising a cache hit ratio from 88% to 95% halves the origin bill, which is usually a cheaper lever than any storage-class change.
What values do I need to enter?
This calculator takes 5 inputs: Viewer requests per month, CDN cache hit ratio, Average object size, GET and SELECT price, Data transfer out to the internet. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Is a Range GET cheaper than a full GET?
The request price is identical, but you are billed only for the bytes actually returned, so range reads cut the transfer component — the part of this bill that is normally the larger of the two.