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.
Inputs
Monthly Read Cost
$95.10
Requests Reaching S3
6,000,000
GET Request Cost
$2.40
Data Transferred Out
1,029.97GB
Data Transfer Cost
$92.70
Step by step
Values used
Viewer requests per month = 50,000,000 requests; CDN cache hit ratio = 88 %; Average object size = 180 KB; GET and SELECT price = 0.0004 USD per 1,000 requests; Data transfer out to the internet = 0.0900 USD per GB
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.
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
How it works
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
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.