
Picking a class without reliable access data is where teams get burned. A bucket full of small or short-lived objects can pick up monitoring charges and never earn them back. A bucket of predictable backups may cost less with a plain lifecycle rule.
This guide covers how Intelligent-Tiering works, its tiers and pricing, a break-even method, when to use or skip it, how it compares with lifecycle policies and other classes, and how to enable and govern it.
Key Takeaways
- Intelligent-Tiering fits unknown, variable, or hard-to-predict access patterns.
- Weigh storage rates against monitoring, request, transfer, and archive-restore costs.
- The three automatic tiers keep millisecond access; the optional archive tiers require restores.
- Object size, retention, latency needs, and recovery expectations decide the right class.
What Is AWS S3 Intelligent-Tiering and How Does It Work?
How the storage class works
You pick Intelligent-Tiering as the storage class when you upload an object. From there, AWS tracks access and moves the object between internal access tiers. No application code changes are needed.
The distinction matters: "Intelligent-Tiering" is the class you select. The tiers inside it are managed by AWS, and objects shift between them as access patterns change.
Access tiers and transition behavior
| Access tier | Moves there after | Access |
|---|---|---|
| Frequent Access | Initial placement | Milliseconds |
| Infrequent Access | 30 days without access | Milliseconds |
| Archive Instant Access | 90 days without access | Milliseconds |
| Archive Access (optional) | 90-730 days, configurable | Restore required; Standard typically 3-5 hours |
| Deep Archive Access (optional) | 180-730 days, configurable | Restore required; Standard typically within 12 hours |
The first three tiers are automatic and have no retrieval fees. The two archive tiers must be enabled explicitly through an Intelligent-Tiering configuration, scoped to a bucket, prefixes, or tags. Enabling that configuration does not move Standard objects into the class.
Archive tiers trade immediate availability for lower prices. If your application can't wait hours for a read, leave them off. Any qualifying access to an archived object promotes it back to Frequent Access after a restore.

Operational rules to know
- Small objects: Objects under 128 KB are never monitored or auto-tiered. They're billed at Frequent Access rates with no monitoring fee.
- Minimum duration: None, and internal tier moves carry no charge.
- Resilience: Designed for 99.999999999% durability and 99.9% availability across at least three Availability Zones.
- Versioning: Current and noncurrent versions need separate lifecycle rules.
- Replication: Requires versioning on both buckets. Objects in the archive tiers can't be replicated until restored and copied to another class.
These operations count as access and promote data to Frequent Access:
- GET, PUT, RestoreObject
- CompleteMultipartUpload, CopyObject, UploadPartCopy
SelectObjectContent resets the timer without promoting the object. HEAD, tagging, and LIST operations do not promote objects.
AWS S3 Intelligent-Tiering Pricing and Cost Calculation
Pricing components
The example below uses US East (N. Virginia), in USD. Rates vary by Region and change over time, so check the AWS pricing page or calculator before deciding.
| Charge | Rate |
|---|---|
| Frequent Access, first 50 TB | $0.023/GB-month |
| Infrequent Access | $0.0125/GB-month |
| Archive Instant Access | $0.004/GB-month |
| Archive Access | $0.0036/GB-month |
| Deep Archive Access | $0.00099/GB-month |
| Monitoring and automation | $0.0025 per 1,000 eligible objects/month |
Requests match S3 Standard: $0.005 per 1,000 PUT/COPY/POST and $0.0004 per 1,000 GET. Internet ingress is free, as are transfers within the same Region. The first 100 GB of monthly internet egress is free.
Monitoring is charged per object, not per byte. That's why object size and distribution decide whether you come out ahead.
Cost trade-offs by tier
- Automatic tiers: AWS describes Infrequent Access as 40% lower cost and Archive Instant as 68% lower, per AWS storage classes. Those are storage claims, not net savings.
- Optional archives: Standard and Bulk retrievals and restore requests are free. Expedited Archive Access retrieval costs $0.03/GB plus $0.01 per request.
- Archive metadata: each archived object adds 8 KB billed at Standard rates and 32 KB at the archive rate.
Break-even calculation
AWS's own Storage Blog example shows the fee arithmetic: 10 million objects larger than 128 KB cost $25/month in monitoring, plus a one-time $100 to transition them in by lifecycle rule at $0.01 per 1,000.
The 128 KB figure sets eligibility. It is not a universal economic break-even size.
Use this method before migrating a production bucket:
- Count objects and estimate average object size.
- Estimate what share of bytes sits idle for 30+ and 90+ days.
- Multiply idle bytes by the savings per GB versus Standard.
- Subtract monitoring ($0.0025 per 1,000 objects, monthly) and the one-time entry cost.
- Factor in retention. Data deleted before 30 days never reaches a cheaper tier.
- Add restore and expedited costs if you enable archive tiers.

If the savings in step 3 exceed the costs in steps 4-6, migrate. If they're close, test on one prefix first.
When to Use and Avoid AWS S3 Intelligent-Tiering
Best-fit workloads
AWS recommends the class for unknown, changing, or unpredictable access, including data lakes, analytics, and new applications. Logs, user-generated content, media libraries, and AI datasets often fit the same profile.
Published customer results show the savings potential on those kinds of workloads:
- Salesforce reports saving millions of dollars annually on a 100+ PB data lake.
- Illumina reports 60% lower storage cost per TB after moving 50 PB.
Evaluate each workload against:
- Access frequency and how often it changes
- Latency and retrieval needs
- Object size (especially around the 128 KB threshold)
- Retention and recovery expectations
- Whether your team can keep lifecycle rules accurate
When another option may be better
- Mostly small objects (under 128 KB) get no tiering benefit.
- Objects deleted within weeks rarely reach a cheaper tier.
- Consistently hot data belongs in S3 Standard.
- Predictable, cold data may cost less in Standard-IA, One Zone-IA, or Glacier with a lifecycle rule.
- Strict immediate-retrieval needs rule out the optional archive tiers.

AWS doesn't forbid Intelligent-Tiering for predictable data. It simply may cost more than a well-tuned fixed rule.
Decision checklist
- Is access unknown or changing? Lean toward Intelligent-Tiering.
- Is access predictable and age-based? Use lifecycle rules.
- Are most objects under 128 KB? Stay in Standard.
- Can the data tolerate hours-long restores? Consider the archive tiers, or a separate Glacier policy.
AWS S3 Intelligent-Tiering vs Lifecycle Policies and Other S3 Classes
Intelligent-Tiering versus lifecycle policies
Intelligent-Tiering reacts to actual reads. Lifecycle policies follow a schedule you define. The two also work together: lifecycle can move objects into Intelligent-Tiering and out to Glacier classes along supported paths.
| Feature | Intelligent-Tiering | Lifecycle rules |
|---|---|---|
| Trigger | Access inactivity | Object age |
| Promotion on access | Automatic | None |
| Cost model | Monitoring fee, no retrieval fee in automatic tiers | Per-object transition fee, destination minimums and retrieval fees |
| Deletion | No | Yes, by age |
Since September 2024, new lifecycle configurations block transitions of objects under 128 KB by default. Lifecycle transition requests cost $0.01 per 1,000 for Intelligent-Tiering, Standard-IA, and One Zone-IA, and up to $0.05 for Deep Archive.
Comparison with fixed S3 storage classes
| Class | Availability | Retrieval | Minimum duration |
|---|---|---|---|
| Standard | 99.99% | Milliseconds | None |
| Intelligent-Tiering | 99.9% | Milliseconds (restore for optional archives) | None |
| Standard-IA | 99.9% | Milliseconds | 30 days |
| One Zone-IA | 99.5%, single AZ | Milliseconds | 30 days |
| Glacier Flexible Retrieval | 99.99% after restore | 1 minute to 12 hours | 90 days |
| Glacier Deep Archive | 99.99% after restore | Within 12 to 48 hours | 180 days |
For steadily accessed data, Standard has no monitoring overhead and is simpler. One Zone-IA is not resilient to the loss of its Availability Zone.
Choosing the best storage class
Ask five questions before you pick a class:
How predictable is access?
How fast must reads be?
What resilience do you need?
How big are the objects?
How long are they kept?
Frequently accessed application data: S3 Standard.
Unpredictable analytics data: Intelligent-Tiering.
Infrequently accessed backups with known patterns: Standard-IA or a lifecycle rule into Glacier.
Long-term compliance archives: Glacier Deep Archive.
How to Enable and Govern AWS S3 Intelligent-Tiering
Enabling the storage class
For new uploads, choose the class at upload time:
aws s3 cp file s3://BUCKET/KEY --storage-class INTELLIGENT_TIERING
s3.put_object(Bucket="BUCKET", Key="KEY", Body=b"data", StorageClass="INTELLIGENT_TIERING")
For existing objects, you have three routes:
- A lifecycle rule with
Transitions: [{"Days":0,"StorageClass":"INTELLIGENT_TIERING"}]inside a complete, enabled rule. - Copy operations that rewrite the object in place.
- S3 Batch Operations Copy for large-scale changes (5 GB per-object limit).
Infrastructure-as-code works too: CloudFormation uses IntelligentTieringConfigurations on AWS::S3::Bucket, and Terraform uses aws_s3_bucket_intelligent_tiering_configuration. Both configure archive tiers only; neither changes an object's class.
Archive configuration and ongoing governance
To enable archive tiers:
aws s3api put-bucket-intelligent-tiering-configuration \
--bucket BUCKET --id archive \
--intelligent-tiering-configuration file://archive.json
{"Id":"archive","Status":"Enabled","Tierings":[{"Days":90,"AccessTier":"ARCHIVE_ACCESS"},{"Days":180,"AccessTier":"DEEP_ARCHIVE_ACCESS"}]}
You need the s3:PutIntelligentTieringConfiguration permission. Test restores before production use.
The minimal restore command is aws s3api restore-object --bucket BUCKET --key KEY --restore-request '{}', with no Days value. A restored object returns to Frequent Access.
Governance practices:
- S3 Storage Lens for storage views by account, Region, class, bucket, and prefix.
- CloudWatch
BucketSizeBytesby storage type (for exampleIntelligentTieringFAStorage,AAStorage). - Cost and Usage Reports with usage types such as
TimedStorage-INT-FA-ByteHrsandMonitoring-Automation-INT. - S3 Inventory to see each object's access tier.
- Operating standards for new buckets, tagging, periodic cost reviews, rollback plans, versions, and replicas.
Block storage alongside S3
Intelligent-Tiering governs object storage. Lucidity does not configure it or replace S3's native controls. The platform focuses on cloud block storage across AWS, Azure, and Google Cloud, with autonomous expansion and shrinking, visibility, and idle-disk detection. Enterprises running EBS volumes alongside S3 may treat it as a complementary layer.
Frequently Asked Questions
What does AWS S3 Intelligent-Tiering do?
It monitors eligible objects' access and moves them between S3 access tiers automatically. Confirm the current tier structure and archive options in AWS documentation.
When should I not use AWS S3 Intelligent-Tiering?
Skip it for consistently hot data, predictable access, mostly small or short-lived objects, and workloads needing a different latency or archival model.
What is the difference between AWS S3 Intelligent-Tiering and lifecycle policies?
Intelligent-Tiering moves objects based on actual access. Lifecycle policies move them on a schedule you set. Use lifecycle when patterns are predictable.
Which Amazon S3 storage class is the best choice?
It depends on access frequency and predictability, latency, resilience, retention, object size, and total cost. No single class wins everywhere.
How do I enable AWS S3 Intelligent-Tiering for existing objects?
Use a lifecycle transition, an in-place copy, or S3 Batch Operations Copy. Test permissions, versions, request charges, and costs first.
Does AWS S3 Intelligent-Tiering charge retrieval fees?
Not in the three automatic tiers. Optional archive tiers need restores; Standard and Bulk are free, but expedited Archive Access retrieval is charged. Verify current pricing.