Task Statement 4.2: Design cost-optimized compute solutions.
📘AWS Certified Solutions Architect – (SAA-C03)
1. What is an Instance Family?
In AWS, an instance family is a group of virtual servers (EC2 instances) designed for a specific type of workload.
Each family is optimized for a particular resource:
- CPU (compute power)
- Memory (RAM)
- Storage (disk performance)
- Networking (data transfer speed)
👉 Key Idea for Exam:
You must choose the instance family that best matches the workload requirement. This helps optimize cost and performance.
2. Why Instance Family Selection Matters
Choosing the wrong instance family can lead to:
- ❌ Paying for unused resources
- ❌ Poor application performance
- ❌ System bottlenecks (CPU, memory, or disk)
Choosing the right one ensures:
- ✅ Cost efficiency
- ✅ High performance
- ✅ Better scalability
3. Main EC2 Instance Families (Very Important for Exam)
You must understand these core families and their use cases.
3.1 General Purpose (Balanced)
Examples: t3, t4g, m5, m6i
Features:
- Balanced CPU, memory, and networking
- Good for most workloads
Use Cases:
- Web servers
- Application servers
- Small databases
- Development and testing environments
Key Concept:
- Burstable (T family):
- Uses CPU credits
- Good for workloads with low baseline + occasional spikes
👉 Exam Tip:
- If question says: “balanced workload” → choose General Purpose
3.2 Compute Optimized
Examples: c5, c6i
Features:
- High CPU performance
- Optimized for compute-intensive tasks
Use Cases:
- Batch processing
- High-performance web servers
- Scientific computing
- Game servers
- Machine learning inference
Key Concept:
- Best when CPU is the bottleneck
👉 Exam Tip:
- If question says: “high CPU usage” or “compute-intensive” → choose Compute Optimized
3.3 Memory Optimized
Examples: r5, r6i, x1
Features:
- Large amount of RAM
- High memory-to-CPU ratio
Use Cases:
- In-memory databases
- Real-time big data analytics
- Caching systems (e.g., Redis-like workloads)
Key Concept:
- Best when application needs fast access to large datasets in memory
👉 Exam Tip:
- If question says: “in-memory”, “large datasets”, “high RAM” → choose Memory Optimized
3.4 Storage Optimized
Examples: i3, i4i, d2, h1
Features:
- High disk I/O performance
- Local (instance store) storage
- Very fast read/write speeds
Use Cases:
- Data warehousing
- Log processing
- Distributed file systems
- NoSQL databases
Key Concept:
- Best when disk performance (IOPS/throughput) is critical
👉 Exam Tip:
- If question says: “high I/O”, “fast disk”, “large data processing” → choose Storage Optimized
3.5 Accelerated Computing
Examples: p3, p4, g4
Features:
- Uses GPUs or specialized hardware
- Very high parallel processing capability
Use Cases:
- Machine learning training
- Video processing
- Graphics rendering
Key Concept:
- Best when workload needs GPU or hardware acceleration
👉 Exam Tip:
- If question says: “GPU”, “AI training”, “graphics” → choose Accelerated Computing
4. Instance Naming Explained (Important)
Example: m5.large
- m → Instance family (General Purpose)
- 5 → Generation (newer = better performance)
- large → Size (CPU, RAM capacity)
👉 Exam Tip:
- Always prefer newer generations (e.g., m6 > m5) unless specified
5. How to Choose the Right Instance Family (Step-by-Step)
Step 1: Identify Bottleneck
Ask:
- CPU-heavy? → Compute Optimized
- Memory-heavy? → Memory Optimized
- Disk-heavy? → Storage Optimized
- Balanced? → General Purpose
- GPU needed? → Accelerated
Step 2: Check Workload Pattern
- Steady workload → Standard instances (m, c, r)
- Variable workload → Burstable (t family)
Step 3: Consider Cost
- Avoid over-provisioning
- Match resources exactly to workload needs
Step 4: Consider Performance Requirements
- Latency-sensitive → high-performance families
- Data-heavy → memory or storage optimized
6. Burstable Instances (Important Concept)
T family (t3, t4g) uses:
- CPU credits system
How it works:
- Earn credits when CPU is low
- Spend credits when CPU spikes
Best For:
- Applications with occasional spikes
Not Good For:
- Constant high CPU workloads
👉 Exam Trap:
If workload is continuously high CPU, do NOT choose T family.
7. Instance Size Scaling
Each family has multiple sizes:
- small → medium → large → xlarge → 2xlarge → etc.
Concept:
- Same family, different capacity
👉 Example:
- m5.large < m5.xlarge < m5.2xlarge
👉 Exam Tip:
- Scale vertically by increasing size
- Scale horizontally using more instances
8. Common Exam Scenarios (Very Important)
Scenario 1:
Application server with moderate usage
👉 Answer: General Purpose
Scenario 2:
CPU-intensive batch job
👉 Answer: Compute Optimized
Scenario 3:
Real-time analytics with large memory usage
👉 Answer: Memory Optimized
Scenario 4:
Heavy disk read/write workload
👉 Answer: Storage Optimized
Scenario 5:
Machine learning model training
👉 Answer: Accelerated Computing
Scenario 6:
Low baseline usage with occasional spikes
👉 Answer: Burstable (T family)
9. Cost Optimization Tips (Exam-Focused)
- Choose smallest instance that meets requirements
- Use burstable instances for variable workloads
- Avoid:
- Overpowered compute for memory workloads
- High-memory instances for CPU-only tasks
👉 Key Rule:
Right-sizing = major cost optimization strategy
10. Key Differences Summary (Quick Revision Table)
| Family | Best For | Key Resource |
|---|---|---|
| General Purpose | Balanced workloads | CPU + RAM |
| Compute Optimized | CPU-heavy tasks | CPU |
| Memory Optimized | Large datasets | RAM |
| Storage Optimized | High disk I/O | Storage |
| Accelerated | AI/ML, GPU tasks | GPU |
11. Final Exam Tips
✔ Always identify what resource is most important
✔ Look for keywords:
- CPU → Compute
- Memory → Memory optimized
- Disk → Storage optimized
✔ Avoid burstable instances for constant workloads
✔ Prefer newer generation instances
✔ Focus on cost vs performance balance
12. One-Line Memory Trick
👉
- CPU → Compute
- RAM → Memory
- Disk → Storage
- Balanced → General
- GPU → Accelerated
