What are the different types of storage classes in S3?
Amazon S3 offers a range of storage classes purpose-built for different use cases, including S3 Standard for frequently accessed data, S3 Intelligent-Tiering for unknown access patterns, and S3 Glacier for long-term archival at the lowest cost .
Amazon S3 offers a variety of storage classes designed to meet different performance, data access, and cost requirements. These classes range from high-performance storage for frequently accessed data to low-cost archival solutions for long-term retention. You can configure storage classes at the object level, and a single S3 bucket can contain objects stored across multiple classes, with the exception of S3 Express One Zone, which requires a specialized directory bucket . S3 Lifecycle policies can also automate transitions between storage classes as data ages .
- 1
General-purpose storage for frequently accessed data with low latency and high throughput performance .
- 2
Designed for 99.99% availability with an availability SLA of 99.9%, and 99.999999999% (11 nines) data durability .
- 3
Ideal for use cases such as cloud applications, dynamic websites, content distribution, mobile and gaming applications, and big data analytics .
- 1
Automatically reduces storage costs by moving objects between access tiers based on changing access patterns, with no performance impact or retrieval fees .
- 2
For a small monthly monitoring and automation charge per object, it monitors access and automatically moves objects not accessed for 30 consecutive days to the Infrequent Access tier, and after 90 days of no access to the Archive Instant Access tier .
- 3
Optional Deep Archive Access tier can be activated to automatically move objects not accessed for 180 days or more, saving up to 95% on storage costs .
- 4
Objects smaller than 128KB can be stored but are always charged at the Frequent Access tier rates, and no monitoring charge applies .
- 1
A high-performance, single-Availability Zone storage class purpose-built for latency-sensitive applications, delivering consistent single-digit millisecond data access .
- 2
Can improve data access speeds by 10x and reduce request costs by up to 80% compared to S3 Standard .
- 3
Data is stored in a different bucket type called an S3 directory bucket, which can support up to 2 million requests per second .
- 4
Optimized for large datasets with many small objects, and integrates with AWS services like Amazon SageMaker and Amazon Athena .
- 1
For data that is accessed less frequently but requires rapid access (milliseconds) when needed .
- 2
Offers the same low latency and high throughput performance as S3 Standard, with a lower per-GB storage price and a per-GB retrieval charge .
- 3
Ideal for long-term storage, backups, and disaster recovery files .
- 1
Similar to S3 Standard-IA but stores data in a single Availability Zone, making it 20% less expensive .
- 2
Ideal for infrequently accessed data that is easily re-creatable or for secondary backup copies, where the risk of data loss from an AZ failure is acceptable .
- 3
Offers the same 99.999999999% durability, but within a single AZ, data can be lost in the event of AZ destruction .
- 1
S3 Glacier Instant Retrieval: For archive data that needs immediate access (milliseconds), such as medical images or news media assets. Offers very cheap storage with retrieval fees .
- 2
S3 Glacier Flexible Retrieval: For rarely accessed long-term data that does not require immediate access. Retrieval options range from minutes to hours, with free bulk retrievals in 5-12 hours .
- 3
S3 Glacier Deep Archive: The lowest-cost storage class in S3, designed for long-term retention and digital preservation of data that may be accessed once or twice a year. Retrieval time is within 12 hours .
Scenario Questions
0-2 years experience
- 1If you need to store user‑uploaded photos that are accessed frequently for the first week and then rarely, which S3 storage class would you choose and why?
- 2How would you set up a lifecycle rule to move objects from the Standard class to Glacier after 90 days of inactivity?
2-5 years experience
- 1Your team noticed a spike in S3 storage costs after enabling versioning. Walk me through how you would use storage classes and lifecycle policies to bring the bill back down.
- 2During a data migration, some objects failed to transition to the Intelligent‑Tiering class. What could cause that, and how would you troubleshoot the issue?
5-8 years experience
- 1Design a multi‑region backup strategy for a petabyte‑scale data lake that balances retrieval latency, durability, and cost using S3 storage classes.
- 2Explain the trade‑offs between Standard‑IA and Glacier Deep Archive for archival logs that need occasional ad‑hoc analysis.
- 3How would you build a system that automatically selects the optimal storage class for each object based on its observed access pattern without manual lifecycle rules?
8+ years experience
- 1Your organization wants to migrate legacy on‑prem archives to S3 while ensuring compliance and minimal cost over a ten‑year horizon. Outline the storage‑class strategy, migration plan, and governance model you would propose.
- 2Discuss how you would evolve a global S3 storage‑class policy across dozens of teams to enforce cost controls, auditability, and future‑proofing as new classes are introduced.
Follow-up Questions
- What metrics would you monitor to verify that your storage‑class policy is delivering the expected cost savings?
- Can you give an example of a situation where you had to override the default storage class for a specific object?
- How would you handle data that must stay in a particular AWS region due to regulatory requirements?