S3 Intelligent-Tiering access tiers
The following section explains the different automatic and optional access tiers. When objects move between access tiers, the storage class remains the same (S3 Intelligent-Tiering).
Frequent Access tier (automatic)
This is the default access tier that any object created or transitioned to S3 Intelligent-Tiering begins its lifecycle in. An object remains in this tier as long as it is being accessed. The Frequent Access tier provides low latency and high-throughput performance.
Infrequent Access tier (automatic)
If an object is not accessed for 30 consecutive days, the object moves to the Infrequent Access tier. The Infrequent Access tier provides low latency and high-throughput performance.
Archive Instant Access tier (automatic)
If an object is not accessed for 90 consecutive days, the object moves to the Archive Instant Access tier. The Archive Instant Access tier provides low latency and high-throughput performance.
Archive Access tier (optional)
S3 Intelligent-Tiering provides you with the option to activate the Archive Access tier for data that can be accessed asynchronously. After activation, the Archive Access tier automatically archives objects that have not been accessed for a minimum of 90 consecutive days. You can extend the last access time for archiving to a maximum of 730 days. The Archive Access tier has the same performance as the S3 Glacier Flexible Retrieval storage class.
Standard retrieval times for this access tier can range from 3–5 hours. If you initiate your restore request by using S3 Batch Operations, your restore starts within minutes. For more information about retrieval options and times, see Restoring objects from the S3 Intelligent-Tiering Archive Access and Deep Archive Access tiers.
Amazon S3 Intelligent-Tiering Access Tiers Comparison
| Feature | Frequent Access (FA) Tier | Infrequent Access (IA) Tier | Archive Instant Access | Archive Access Tier | Deep Archive Access Tier |
|---|---|---|---|---|---|
| Intended Use | Frequently accessed data | Infrequently accessed data | Rarely accessed but need quick retrieval | Data archived for infrequent use | Long-term data storage, rare retrieval |
| Storage Cost | Higher cost | Lower than FA | Lower than IA | Lower than IA | Lowest cost |
| Retrieval Cost | No retrieval cost | $0.01 per GB | $0.02 per GB | $0.02 per GB | $0.03 per GB |
| Access Latency | Millisecond | Millisecond | Millisecond | Hours (12 hours) | Hours (12 hours) |
| Use Case | Real-time data, frequently accessed | Backups, infrequently used data | Quick access to archived data | Long-term archival storage with slower access | Very low-cost storage for regulatory or long-term archival |
| Monitoring and Automation Cost | $0.0025 per 1,000 objects/month | $0.0025 per 1,000 objects/month | $0.0025 per 1,000 objects/month | $0.0025 per 1,000 objects/month | $0.0025 per 1,000 objects/month |
| Minimum Storage Duration | None | 30 days | 90 days | 90 days | 180 days |
S3 Lifecycle Policies vs S3 Intelligent-Tiering
| Feature | S3 Lifecycle Policies | S3 Intelligent-Tiering |
|---|---|---|
| Purpose | Manage data lifecycle (transition, expiration, deletion) | Optimize cost by automatically moving data based on access patterns |
| Storage Classes | Can transition data to any S3 storage class (e.g., STANDARD, GLACIER, DEEP_ARCHIVE, IA) | Moves data between Frequent Access and Infrequent Access + 2 |
| Automation | Requires manual configuration of transitions and expirations | Automatically moves objects between two access tiers |
| Cost | Cost savings come from manually managing transitions and expirations | Small additional cost for monitoring and automation; cost savings from efficient storage |
| Access Pattern | Works based on pre-defined rules (time-based) | Works based on real-time access patterns |
| Data Deletion | Can expire and delete objects based on age or version | No data expiration; objects stay in the two access tiers |
| Use Case | Long-term retention, archival, or compliance policies | Optimizing cost for unpredictable or variable access patterns |
| Granularity | Flexible: You can define rules per prefix, tag, or object | Automatic based on access patterns, no user intervention needed |