Learning Update: Understanding Amazon S3 Storage Classes ☁️
My journey of S3 and its tiers
As part of my AWS learning journey, today I spent some time understanding Amazon S3 Storage Classes and how AWS allows us to choose different storage options depending on how frequently data is accessed, how quickly it needs to be retrieved, and how much we want to optimize storage costs.
At first, I thought S3 was simply "cloud storage," but learning about storage classes made me realize how important data access patterns are when designing a cost-efficient cloud architecture.
Here’s what I learned today:
🟢 S3 Standard
This is the default storage class and is designed for frequently accessed data with millisecond access.
A good example would be application assets, frequently accessed datasets, or active files.
🟡 S3 Intelligent-Tiering
This one was particularly interesting to me.
Instead of manually deciding how frequently an object will be accessed, Intelligent-Tiering monitors access patterns and automatically moves objects between access tiers to optimize storage costs.
This makes it useful when the access pattern is unknown, changing, or unpredictable. AWS currently provides frequent, infrequent, and archive-related tiers within Intelligent-Tiering.
🔵 S3 Standard-IA
"IA" means Infrequent Access.
This is designed for data that is stored for a longer period but accessed less frequently, while still requiring millisecond retrieval.
For example:
Backups that occasionally need to be restored.
It provides multi-AZ resilience but has retrieval charges and a minimum storage duration.
🟠 S3 One Zone-IA
Similar to Standard-IA, but the data is stored in a single Availability Zone.
The advantage is lower storage cost, but the trade-off is lower resilience because the data isn't protected against the physical loss of that Availability Zone.
This makes more sense for data that can be recreated, such as secondary copies or certain intermediate datasets.
⚡ S3 Express One Zone
This was another interesting class to learn about.
It's designed for very latency-sensitive workloads that need extremely fast access within a single Availability Zone.
So unlike normal S3, the focus here isn't primarily on cheap long-term storage — it's on high-performance object storage.
❄️ S3 Glacier Instant Retrieval
This is designed for rarely accessed archival data that still needs millisecond retrieval.
A good example could be medical images or other historical datasets that aren't accessed frequently but need to be available immediately when required.
🧊 S3 Glacier Flexible Retrieval
This is intended for long-term archives where data may only need to be retrieved occasionally.
Unlike Glacier Instant Retrieval, archived objects need to be restored before they can be accessed, with retrieval typically taking minutes to hours depending on the retrieval option.
🧊 S3 Glacier Deep Archive
This is designed for data that is accessed very rarely, potentially less than once a year.
It's particularly useful for long-term archival and preservation where minimizing storage cost is more important than immediate access. Objects need to be restored before they can be accessed.
What I took away
The biggest lesson for me today was:
Choosing an S3 storage class is essentially a trade-off between access frequency, retrieval speed, resilience, and cost.
A simple way I'm remembering it is:
Frequently accessed → S3 Standard
Unknown/changing access → Intelligent-Tiering
Infrequent but quick access → Standard-IA / One Zone-IA
Rarely accessed → Glacier classes
Extremely rare, long-term archival → Glacier Deep Archive
AWS also allows Lifecycle Policies to automatically transition objects between storage classes as they become less frequently accessed, which means we don't necessarily have to manage these transitions manually.
I'm continuing my AWS journey and currently working toward AWS Certified Cloud Practitioner (CLF-C02). Looking forward to learning more about how these services fit together when designing real-world cloud architectures. 🚀
#AWS #AWSBuilderCenter #AWSStudent #AWSCommunity #AmazonS3 #CloudComputing #AWSCloudPractitioner #LearningInPublic
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article