When is a colder tier worth it?

When you rarely read the data. The break-even retrieval volume shown is where the retrieval charges eat the storage saving; above it the colder tier costs more.

Why is my bill dominated by requests?

Many small objects. Request charges are per operation regardless of size, so a million tiny objects can cost more in requests than in storage.

Technologycloud

Object Storage Cost Calculator

Object storage cost across tiers, with the retrieval charge included. A colder tier is only cheaper if you rarely read the data, and the break-even retrieval volume is the number that decides it.

Also called: s3 cost calculator, blob storage pricing.

Monthly cost

₹10,952

₹10,952 a month: ₹10,752 storage, ₹0 retrieval and ₹200 requests. On the standard tier it would be ₹10,952, so this tier saves ₹0 on storage but adds ₹0 in retrieval. The standard tier has no retrieval charge, which suits data read regularly.

Storage

₹10,752

Retrieval

₹0

Requests

₹200

On the standard tier

₹10,952

Storage saved by the tier

₹0

Retrieval at which the tier stops paying

₹0

On tier choice

The standard tier has no retrieval charge, which suits data read regularly.

On prices

Prices are inputs, not constants. Provider pricing changes continuously, so take the current rate from the provider calculator rather than relying on a default here.

How this is calculated

Method and background

How this is calculated

Cold tiers trade a lower per-gigabyte monthly rate for a retrieval charge and often a minimum storage duration. That makes them cheaper for backups and archives and more expensive for anything read regularly. The break-even shown is the monthly retrieval volume at which the retrieval charges consume the storage saving, and retrieving above it means the colder tier is costing more. Request charges matter for workloads with many small objects, where they can exceed the storage cost entirely.

a cheaper storage tier trades a lower monthly rate for a retrieval charge, so access frequency decides

s: Stored GB
r: Retrieved GB

Worked examples

Each of these is asserted on every build. If a change to the engine ever moved one of these answers, the build would fail before the page could print it.

5 TB on the standard tier

Data stored: 5 TB
Storage class: Standard
Standard per GB month: ₹2
Infrequent per GB month: ₹1
Archive per GB month: ₹0
Retrieval charge per GB: ₹1
Data retrieved a month: 100 GB
Requests a month, thousands: 500
Cost per thousand requests: ₹0

Monthly cost₹10,952

5120 GB x 2.1

Open this example

the archive tier adds retrieval

Data stored: 5 TB
Storage class: Archive
Standard per GB month: ₹2
Infrequent per GB month: ₹1
Archive per GB month: ₹0
Retrieval charge per GB: ₹1
Data retrieved a month: 100 GB
Requests a month, thousands: 500
Cost per thousand requests: ₹0

Monthly cost₹2,082

boundary: the retrieval volume where the tier stops paying

Open this example

Method and limits

What it assumes

No minimum storage duration penalty, which several archive tiers apply.

What it deliberately does not model

Archive tiers have minimum storage durations and early deletion charges.
Retrieval from archive can take hours, which is a service constraint rather than a cost one.
Lifecycle transition requests are themselves charged.

Formula version 1.0.0 · definition 1.0.0 · India · Report a problem with this calculator

Frequently asked questions

When is a colder tier worth it?: When you rarely read the data. The break-even retrieval volume shown is where the retrieval charges eat the storage saving; above it the colder tier costs more.
Why is my bill dominated by requests?: Many small objects. Request charges are per operation regardless of size, so a million tiny objects can cost more in requests than in storage.