S3 Intelligent-Tiering saves on large objects with unpredictable access and costs more on millions of tiny objects or predictable data. It charges a monitoring and automation fee of $0.0025 per 1,000 objects per month, $2.50 per million, and never tiers down objects smaller than 128 KB, which still bill at the Frequent Access rate. For data whose access you cannot predict, the automatic move to cooler tiers outweighs the fee. For data with a known, time-based access pattern, a fixed storage class or a lifecycle policy with no per-object fee is cheaper. Match the tool to the access pattern and the object size.
Last updated: June 2026 · Written by Fredrik Filipsson and reviewed by Morten Andersen · See, Cut, Lock, Run method
Amazon S3 Intelligent-Tiering is a storage class that automatically moves objects between access tiers based on how often they are read, so you do not have to predict access patterns or manage lifecycle rules. It is genuinely useful for the right data, but it carries a per-object monitoring fee and a minimum object size that make it the wrong choice for some workloads. This explainer is part of our complete guide to AWS cost optimization, the cluster pillar it links up to.
What is S3 Intelligent-Tiering and how does it work?
S3 Intelligent-Tiering is an S3 storage class that monitors each object's access and shifts it between tiers automatically to lower cost without retrieval fees on the frequent and infrequent tiers. An object starts in the Frequent Access tier; after 30 consecutive days without access it moves to Infrequent Access, after 90 days to Archive Instant Access, and you can optionally enable Archive Access at 90-plus days and Deep Archive Access at 180-plus days for asynchronous retrieval. AWS charges a small monitoring and automation fee per object instead of a retrieval fee on the instant tiers, which is what makes it appealing for data you read unpredictably. Confirm the current tier thresholds and fees against the Amazon S3 pricing page, since these change over time.
When does S3 Intelligent-Tiering save money?
It saves when objects are large and their access pattern is unknown or changing, which is exactly the case it was designed for. If you would otherwise leave a dataset in S3 Standard because you cannot predict which objects will go cold, Intelligent-Tiering captures the saving automatically: any object that stops being read drops to a cheaper tier within 30 days, and the monitoring fee on a large object is trivial against the storage saved. Data lakes, user-generated content, backups with irregular restores, and long-tail media libraries all fit. The saving is real because the automation does the tiering you would never get around to doing by hand, and because there is no retrieval fee on the frequent and infrequent tiers, an object that goes cold and is then read again does not punish you. For the request-cost side of these same buckets, see the sibling guide how to reduce Amazon S3 request and API costs.
When does S3 Intelligent-Tiering cost more?
It costs more when you store huge numbers of tiny objects or data whose access pattern you already know. The monitoring and automation fee is $0.0025 per 1,000 objects per month, so a bucket of one billion small objects adds $2,500 a month in monitoring alone, before any storage. Worse, objects smaller than 128 KB are never moved to a cooler tier, so they keep paying the Frequent Access rate while, on larger objects, you would at least earn the tiering benefit. And when the access pattern is predictable, time-based and known, you do not need monitoring at all: a lifecycle policy transitions objects on a schedule with no per-object fee. The table below frames the decision.
| Decision criterion | Intelligent-Tiering saves | Intelligent-Tiering costs more |
|---|---|---|
| Object size | Large, mostly above 128 KB | Mostly tiny, under 128 KB |
| Object count | Moderate count of larger files | Millions or billions of small objects |
| Access pattern | Unknown or changing | Known and time-based |
| Retrieval needs | Irregular reads of cooled data | Predictable, scheduled access |
| Better alternative | None; this is the right tool | Fixed class or lifecycle policy |
The verdict: use Intelligent-Tiering for large objects with unpredictable access, and reach for a fixed storage class or a lifecycle policy when objects are tiny or the access pattern is already known.
Objects under 128 KB are not monitored, not charged the fee, and never tiered down, which sounds harmless but means a bucket of millions of small files gets zero benefit from Intelligent-Tiering while still sitting at Frequent Access rates. Aggregate small objects or pick a fixed class instead.
Not sure if Intelligent-Tiering is helping or hurting?
Our AWS cost audit analyzes your object size distribution and access patterns by bucket, picks the right storage class or lifecycle policy for each, and proves the storage saving before any change. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →Should I use Intelligent-Tiering or a lifecycle policy?
Use Intelligent-Tiering when access is unpredictable and a lifecycle policy when the access pattern is known and time-based. A lifecycle policy transitions objects to a cooler class after a fixed age, say move to Standard-Infrequent Access at 30 days and Glacier at 90, and it carries no per-object monitoring fee, only a one-time transition request charge. That makes lifecycle the cheaper choice whenever you can confidently say "this data is cold after N days," such as logs, compliance archives, and backups with a fixed retention. Intelligent-Tiering earns its fee only when you genuinely cannot predict access and would otherwise overpay by leaving everything hot. A common mistake is enabling Intelligent-Tiering on predictable data where a simple lifecycle rule would have done the same job for free. For the broader storage-cost picture, our data-cost cluster work covers this in depth alongside the AWS guidance here.
The AWS Cost Optimization Field Guide includes the S3 storage-class decision tree we run on every bucket, so each dataset lands in the class that is actually cheapest for its size and access pattern.
Frequently asked questions
When does S3 Intelligent-Tiering save money?
It saves when objects are large, at least 128 KB, and have unknown or changing access patterns, because the automatic move to cooler tiers after 30, 90, and 180 days of no access outweighs the small per-object monitoring fee. It is built for data you cannot predict, where you would otherwise leave everything in S3 Standard.
When does S3 Intelligent-Tiering cost more?
It costs more when you store millions of tiny objects or data with a known access pattern. The monitoring fee is $0.0025 per 1,000 objects per month, so billions of small objects add a large fee, and objects under 128 KB are never tiered down yet still count. For predictable data, a fixed class or a lifecycle policy is cheaper.
How much is the S3 Intelligent-Tiering monitoring fee?
The monitoring and automation fee is $0.0025 per 1,000 objects monitored per month, which is $2.50 per million objects. Objects smaller than 128 KB are not monitored or charged the fee, but they are also never moved to a cooler tier and always bill at the Frequent Access rate.
Should I use Intelligent-Tiering or a lifecycle policy?
Use Intelligent-Tiering when access is unpredictable and you want AWS to move data automatically. Use a lifecycle policy when the access pattern is known and time-based, since a lifecycle rule that transitions objects after a set age has no per-object monitoring fee and is cheaper for predictable data.
The short version
S3 Intelligent-Tiering is the right tool for large objects with unpredictable access and the wrong tool for millions of tiny objects or predictable, time-based data. The $0.0025 per 1,000 objects monitoring fee and the 128 KB minimum decide which side you are on. Match the storage class to object size and access pattern, and use a lifecycle policy where access is known. When you want every bucket placed in the class that is genuinely cheapest, that is the work our AWS cost optimization service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: AWS pricing ↗, AWS documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.