Task Statement 3.1: Determine high-performing and/or scalable storage solutions.
📘AWS Certified Solutions Architect – (SAA-C03)
1. Overview of Storage Types
There are three main storage types in AWS:
| Storage Type | AWS Example | Best For |
|---|---|---|
| Object Storage | Amazon S3 | Scalable storage, backups, static content |
| File Storage | Amazon EFS | Shared file systems |
| Block Storage | Amazon EBS | Databases, OS disks |
2. Object Storage
What is Object Storage?
Object storage stores data as objects inside buckets.
Each object contains:
- Data (file content)
- Metadata (information about the file)
- Unique ID
Key Characteristics
- Highly scalable (virtually unlimited storage)
- Stores data in a flat structure (no folders like traditional systems)
- Accessed via HTTP/HTTPS (REST API)
- High durability (11 9’s in S3)
- Not suitable for low-latency frequent updates
AWS Service
- Amazon S3 (Simple Storage Service)
Performance Characteristics
- High throughput
- High latency compared to block storage
- Optimized for read-heavy workloads
- Supports parallel access
Use Cases (IT-focused)
- Storing application logs
- Static website hosting
- Backup and archive storage
- Data lakes and analytics workloads
Important Exam Points
- S3 is not a file system
- Cannot mount S3 as a disk (without special tools)
- Best for unstructured data
- Supports lifecycle policies and storage classes
3. File Storage
What is File Storage?
File storage organizes data in a hierarchical structure:
- Files
- Directories (folders)
It behaves like a traditional file system.
Key Characteristics
- Supports shared access
- Multiple servers can access the same files simultaneously
- Uses standard protocols:
- NFS (Linux)
- SMB (Windows)
AWS Services
- Amazon EFS (Elastic File System) → Linux
- Amazon FSx → Windows & other file systems
Performance Characteristics
- Medium latency
- Scales automatically (EFS)
- Good for concurrent access
- Supports file locking and permissions
Use Cases (IT-focused)
- Web servers sharing files
- Content management systems
- Development environments
- Shared application storage
Important Exam Points
- EFS = serverless + scalable
- Can be mounted on multiple EC2 instances
- Best for shared workloads
- Supports POSIX permissions
4. Block Storage
What is Block Storage?
Block storage divides data into fixed-size blocks and stores them separately.
Each block:
- Has a unique address
- Is managed by the OS
Key Characteristics
- Very low latency
- High performance
- Acts like a hard drive
- Data is accessed at block level
AWS Service
- Amazon EBS (Elastic Block Store)
Performance Characteristics
- High IOPS (Input/Output Operations Per Second)
- Low latency
- Optimized for transactional workloads
- Supports different volume types (SSD, HDD)
Use Cases (IT-focused)
- Databases (MySQL, PostgreSQL)
- Boot volumes (OS disks)
- High-performance applications
- Transactional systems
Important Exam Points
- EBS is attached to EC2
- Typically used by one instance at a time
- Requires file system formatting (ext4, NTFS)
- Supports snapshots (backup to S3)
5. Key Differences (Very Important for Exam)
| Feature | Object Storage (S3) | File Storage (EFS/FSx) | Block Storage (EBS) |
|---|---|---|---|
| Structure | Flat (objects) | Hierarchical | Blocks |
| Access Method | API (HTTP) | NFS/SMB | Attached to OS |
| Scalability | Unlimited | Scales (EFS auto) | Limited to volume size |
| Latency | High | Medium | Low |
| Performance | Throughput-based | Balanced | High IOPS |
| Sharing | Yes (via API) | Yes (multi-instance) | Limited |
| Best For | Static data, backups | Shared file systems | Databases, OS |
6. When to Choose Which (Exam Decision Guide)
Choose Object Storage (S3) when:
- You need massive scalability
- Data is unstructured
- You need cost-effective storage
- Access is via API
Choose File Storage (EFS/FSx) when:
- Multiple servers need shared access
- Applications require a file system
- You need concurrent access
Choose Block Storage (EBS) when:
- You need high performance and low latency
- Running databases
- You need a boot disk for EC2
7. Common Exam Traps
- ❌ Trying to use S3 as a file system → Not correct
- ❌ Using EBS for shared access across multiple EC2 → Limited support
- ❌ Using EFS for high-performance database workloads → Not optimal
- ❌ Ignoring latency requirements when choosing storage
8. Quick Memory Tips (For Exam)
- S3 = Scalable + Simple storage
- EFS = Elastic shared files
- EBS = EC2 disk (block storage)
Final Summary
- Object storage (S3) → Best for scalability and unstructured data
- File storage (EFS/FSx) → Best for shared file systems
- Block storage (EBS) → Best for high-performance workloads
