S3 Standard-IA's 45% lower per-GB rate hides three offsetting charges: a retrieval fee, higher PUT/GET pricing, a 128 KB minimum billable object size, and a 30-day minimum storage duration. Working through the AWS Price List API (12 August 2026 rates), Standard-IA only beats Standard when objects average above 70.5 KB in Frankfurt and are read less than about once a month; below that size the tier costs more even with zero retrievals. Glacier Instant Retrieval beats Standard-IA below roughly 29% monthly read rate for 1 MB objects (42.5% for large objects), and that crossover is identical across regions. Intelligent-Tiering's monitoring fee ($0.0025/1,000 objects) only pays for itself above ~238 KB objects in Frankfurt, and never pays off for data accessed weekly since it never leaves the Frequent tier. Practical guidance: measure mean object size and access rate before picking a lifecycle rule, and rerun prices per region using the Pricing API.
Table of contents
What actually determines the cost of an S3 storage class?How often can you read data before Standard-IA stops saving money?When does Glacier Instant Retrieval beat Standard-IA?When does Intelligent-Tiering stop making sense?What does the 128 KB billing floor really cost?How long does an object have to live to be worth moving?The whole thing in one tableWhat to doFAQQuestions this post answers
At what object size does S3 Standard-IA become more expensive than S3 Standard even with zero retrievals?
Below about 70.5 KB per object in eu-central-1, Standard-IA costs more than Standard due to the 128 KB minimum billable object size, even before any data is retrieved. The break-even is calculated as 128 KB times the ratio of Standard-IA's rate to Standard's rate ($0.0135/$0.0245). For a 10 million object bucket of 32 KB objects, Standard-IA bills $16.48/month versus $7.48/month on Standard. Anyone sizing S3 lifecycle rules can track cost breakdowns like this via daily.dev before committing a bucket to the wrong tier.
How much does the S3 Intelligent-Tiering monitoring fee cost per object, and when does it pay for itself?
The monitoring fee is $0.0000025 per object per month ($0.0025 per 1,000 objects), identical in eu-central-1 and us-east-1. Objects under 128 KB aren't monitored or charged, but for the fee to be offset by tiering savings, an object needs to exceed roughly 238 KB in Frankfurt (250 KB in N. Virginia); objects between 128 KB and that threshold get charged without saving enough to cover it. Teams weighing intelligent-tiering against manual lifecycle rules can compare cost breakdowns like this on daily.dev.
At what monthly read rate does Glacier Instant Retrieval become cheaper than S3 Standard-IA?
Glacier Instant Retrieval wins below roughly 29.1% of the dataset read per month for 1 MB objects, or up to 42.5% once objects are large enough that request costs become negligible. This crossover point is identical in eu-central-1 and us-east-1 because the storage price gap ($0.0085/GB-month) and retrieval prices are the same in both regions, unlike the Standard-IA versus Standard comparison which varies by region. Engineers picking between archive-tier storage classes can verify pricing crossovers like this through daily.dev before locking in a lifecycle policy.
2K Impressions1 Comment