S3 Request Cost Calculator

Work out s3 request cost instantly with clear inputs, formula shown and shareable results.

About S3 Request Cost Calculator

Object storage request pricing charges writes roughly ten times more than reads, so a workload with far fewer PUTs can still spend more on them. This is why writing millions of tiny objects is expensive relative to their storage cost, and why batching small records into larger objects is one of the most effective object-storage optimisations.

Formula

Request cost

GET cost = GET requests / 1000 x GET price; PUT cost = PUT requests / 1000 x PUT price

Worked example

With the default values below, S3 Request Cost Calculator returns Monthly request cost of $88.00. Change any input above and every figure here is recalculated in your browser.

Inputs used

GET requests per monthminimum 0 millions: 120 millions
PUT requests per monthminimum 0 millions: 8 millions
GET price per 1,000 requestsminimum 0: 0.0004
PUT price per 1,000 requestsminimum 0: 0.005

Results

Monthly request cost: $88.00
GET request cost: $48.00
PUT request cost: $40.00
Share of cost from writes: 45.5%

Step by step

1Values used
2Request cost
3Monthly request cost= 88.00
4GET request cost= 48.00
5PUT request cost= 40.00
6Share of cost from writes= 45.5

Assumptions and limits

The result is derived only from the 4 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

Why are PUTs so much more expensive?

A write must be durably replicated across multiple facilities before acknowledgement, which is far more work than serving a read from any replica.

Do LIST operations count as reads?

They are priced as PUT-class requests on most providers, and a LIST over a large prefix is far more expensive than a single GET. Avoid listing in hot paths.