Task Statement 4.1: Design cost-optimized storage solutions.
📘AWS Certified Solutions Architect – (SAA-C03)
When designing cost-optimized storage solutions in AWS, one of the key skills is selecting the right storage tier for your data. Choosing the correct tier helps balance cost, performance, and accessibility.
Think of a storage tier as a “level” or “class” of storage that is optimized for specific use cases. AWS offers multiple storage services, each with different tiers that differ in cost, durability, access speed, and use case.
1. Understanding the Factors for Choosing a Storage Tier
Before picking a storage tier, you should consider these main factors:
- Frequency of Access
- How often will the data be used?
- Frequently accessed → use higher-performance tiers.
- Rarely accessed → use lower-cost, infrequent access or archive tiers.
- Performance Requirements
- Does your application need fast read/write speeds?
- High-performance workloads (like databases) require faster storage tiers.
- Durability and Availability
- Durability is the chance your data will remain safe (e.g., multiple copies in AWS regions).
- Availability is how quickly the data can be accessed when needed.
- Cost
- Higher performance usually costs more.
- Infrequent or archival storage costs less but may have slower access.
- Compliance and Retention
- Some data must be retained for years (regulatory reasons).
- Archival tiers are cheaper for long-term retention.
2. AWS Storage Services and Tiers
AWS provides multiple storage services. Each has its own tiers suitable for different scenarios.
A. Amazon S3 (Simple Storage Service)
S3 is object storage – think of it as storing files like logs, backups, images, or database exports.
S3 Storage Classes (Tiers)
| Tier | Cost | Access Frequency | Latency / Retrieval | Use Case Example |
|---|---|---|---|---|
| S3 Standard | High | Frequent | Milliseconds | Active files, web content |
| S3 Intelligent-Tiering | Medium | Unknown / Mixed | Milliseconds | Automatically moves objects between tiers based on usage |
| S3 Standard-Infrequent Access (IA) | Medium-Low | Infrequent | Milliseconds | Backups or older project files |
| S3 One Zone-IA | Low | Infrequent | Milliseconds | Non-critical infrequently accessed data |
| S3 Glacier Instant Retrieval | Very Low | Rare | <1 second | Archived data with occasional access |
| S3 Glacier Flexible Retrieval | Very Low | Rare | Minutes to hours | Long-term archives |
| S3 Glacier Deep Archive | Lowest | Rare | Up to 12 hours | Data stored for years (regulatory/compliance) |
Key points for S3 tiers:
- Frequent access → Standard
- Infrequent access → Standard-IA or One Zone-IA
- Archival → Glacier tiers
- Intelligent-Tiering → automatically saves cost without manual lifecycle policies
B. Amazon EBS (Elastic Block Store)
EBS provides block storage for EC2 instances (like virtual hard drives).
EBS Volume Types
| Type | Cost | Use Case |
|---|---|---|
| General Purpose SSD (gp3) | Moderate | Most workloads, general-purpose storage for EC2 |
| Provisioned IOPS SSD (io2) | High | Databases or apps needing high IOPS (input/output operations per second) |
| Throughput Optimized HDD (st1) | Low | Big data, logs, streaming data |
| Cold HDD (sc1) | Lowest | Less frequently accessed data |
Key points:
- High-performance apps → gp3 or io2
- Large, sequential access workloads → st1
- Rare access → sc1
C. Amazon EFS (Elastic File System)
EFS is file storage for EC2 instances, accessible via NFS.
EFS Storage Classes
| Tier | Cost | Access Frequency |
|---|---|---|
| EFS Standard | High | Frequently accessed files |
| EFS Infrequent Access (EFS IA) | Low | Files accessed less often |
| EFS Lifecycle Management | Optimizes cost automatically by moving cold files to IA | Mixed access |
Key points:
- Use Standard for live application files.
- Use IA for older, less used files.
- Lifecycle management automatically saves money.
D. AWS Backup and Archival Options
- AWS Backup integrates with S3, EBS, EFS, and RDS.
- Can move old backups to Glacier or S3 IA to reduce costs.
3. Practical Exam Tips
- Know access patterns
- Example: Logs accessed once a month → S3 Standard-IA or Glacier.
- Database data used constantly → EBS gp3 or io2.
- Understand retrieval time vs cost
- Faster access → higher cost.
- Slower access → cheaper storage tier.
- Look for automated options
- S3 Intelligent-Tiering and EFS lifecycle policies help reduce manual intervention.
- Match storage type with workload
- File system → EFS
- Block storage → EBS
- Object storage → S3
- One exam trick
- Question may give you data access patterns and retention policies.
- Identify which tier gives lowest cost while meeting access requirements.
4. Summary
- AWS storage tiers are cost vs access trade-offs.
- Pick a tier based on:
- Frequency of access
- Performance requirements
- Durability and availability
- Retention and compliance
- Use automated tiers like S3 Intelligent-Tiering or EFS Lifecycle for cost efficiency.
- Remember: Frequent access = high cost, rare access = low cost.
