Introduction

AWS Well-Architected Framework

The AWS Well-Architected Framework is a comprehensive guide for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud. It provides a consistent approach for customers and partners to evaluate architectures and implement scalable designs.

Six Pillars of the Well-Architected Framework

  1. Operational Excellence: Running and monitoring systems to deliver business value
  2. Security: Protecting information, systems, and assets
  3. Reliability: Ensuring workload performs intended function correctly and consistently
  4. Performance Efficiency: Using computing resources efficiently
  5. Cost Optimization: Avoiding unnecessary costs
  6. Sustainability: Minimizing environmental impacts

For this midterm exam, focus is on four core pillars:

🔐 1. Security Pillar

Key Principle: Protect data, systems, and assets while delivering business value through risk assessments and mitigation strategies.

Core Components:

  • Identity and Access Management (IAM): Control who can do what in your AWS environment
  • Detective Controls: Identify security threats and events (GuardDuty, CloudTrail)
  • Infrastructure Protection: Protect compute resources (Security Groups, NACLs)
  • Data Protection: Encrypt data at rest and in transit (KMS, SSL/TLS)
  • Incident Response: Respond effectively to security incidents

Best Practices:

  • ✅ Implement strong identity foundation (least privilege principle)
  • ✅ Enable traceability (CloudTrail, VPC Flow Logs)
  • ✅ Apply security at all layers (defense in depth)
  • ✅ Automate security best practices
  • ✅ Protect data in transit and at rest
  • ✅ Keep people away from data (use roles, not credentials)
  • ✅ Prepare for security events

🔄 2. Reliability Pillar

Key Principle: Ensure a workload performs its intended function correctly and consistently when expected, with the ability to operate and test through its total lifecycle.

Core Components:

  • Foundations: Sufficient network bandwidth, adequate compute quotas
  • Workload Architecture: Distributed systems design, Multi-AZ deployment
  • Change Management: Monitor resources, implement Auto Scaling
  • Failure Management: Backup data, test recovery procedures, automate recovery

Best Practices:

  • ✅ Automatically recover from failure
  • ✅ Test recovery procedures
  • ✅ Scale horizontally to increase aggregate workload availability
  • ✅ Stop guessing capacity (use Auto Scaling)
  • ✅ Manage change through automation (Infrastructure as Code)

Key Metrics:

  • RTO (Recovery Time Objective): Maximum acceptable downtime
  • RPO (Recovery Point Objective): Maximum acceptable data loss

⚡ 3. Performance Efficiency Pillar

Key Principle: Use computing resources efficiently to meet system requirements and maintain efficiency as demand changes and technologies evolve.

Core Components:

  • Selection: Choose the right resource types and sizes based on workload requirements
  • Review: Continuously review choices as AWS evolves
  • Monitoring: Monitor performance to identify bottlenecks
  • Tradeoffs: Understand tradeoffs (consistency vs latency, durability vs time)

Best Practices:

  • ✅ Democratize advanced technologies (use managed services)
  • ✅ Go global in minutes (multi-region deployment)
  • ✅ Use serverless architectures (Lambda, Fargate)
  • ✅ Experiment more often (easy to test new resources)
  • ✅ Consider mechanical sympathy (understand how services work)

Resource Types:

  • Compute: EC2, Lambda, ECS, Fargate
  • Storage: S3, EBS, EFS, FSx
  • Database: RDS, DynamoDB, ElastiCache, Redshift
  • Network: CloudFront, Route 53, Global Accelerator

💰 4. Cost Optimization Pillar

Key Principle: Avoid unnecessary costs while achieving business outcomes at the lowest price point.

Core Components:

  • Practice Cloud Financial Management: Implement financial accountability
  • Expenditure and Usage Awareness: Understand and control costs
  • Cost-Effective Resources: Use the right size and type of resources
  • Manage Demand and Supply Resources: Optimize supply to meet demand
  • Optimize Over Time: Continuously improve and adopt new services

Best Practices:

  • ✅ Implement cloud financial management
  • ✅ Adopt a consumption model (pay for what you use)
  • ✅ Measure overall efficiency
  • ✅ Stop spending money on undifferentiated heavy lifting
  • ✅ Analyze and attribute expenditure (use tags, Cost Explorer)

Cost Optimization Strategies:

  • Right-sizing instances
  • Using Reserved Instances and Savings Plans
  • Implementing Auto Scaling
  • Using S3 Lifecycle policies
  • Leveraging spot instances for fault-tolerant workloads

Key AWS Concepts to Master

Shared Responsibility Model

AWS Responsibility (Security OF the Cloud):

  • Physical infrastructure security
  • Hardware and software infrastructure
  • Network infrastructure
  • Managed services (RDS, Lambda)

Customer Responsibility (Security IN the Cloud):

  • Data encryption
  • Platform and application management
  • Operating system, network, and firewall configuration
  • IAM permissions
  • Client-side and server-side encryption

AWS Global Infrastructure

Components:

  1. Regions: Geographic areas (e.g., us-east-1, eu-west-1)

    • 33+ regions worldwide (as of 2024)
    • Choose based on: compliance, latency, pricing, service availability

  2. Availability Zones (AZs): One or more discrete data centers

    • Multiple AZs per region (minimum 3, typically 6)
    • Isolated from failures in other AZs
    • Connected with low-latency links
    • Design for Multi-AZ deployment for high availability

  3. Edge Locations: CDN endpoints for CloudFront

    • 450+ edge locations in 90+ cities
    • Cache content closer to users
    • Reduce latency for global users

Core AWS Services (Exam Critical)

For comprehensive, in-depth coverage of these core services including instance types, pricing models, limits, architecture patterns, and exam tips, see the AWS Service Fundamentals section.

Compute:

  • EC2: Virtual servers with 5 main instance families (T3, M6i, C6i, R6i, I4i), 6 pricing models (On-Demand, Reserved, Savings Plans, Spot, Dedicated)
  • Lambda: Serverless compute with 15-minute timeout, 10 GB memory max, event-driven architecture
  • ECS/Fargate: Container orchestration - Fargate for serverless containers, ECS for managed Docker
  • Auto Scaling: Automatic capacity adjustment with target tracking, step scaling, and scheduled policies

Storage:

  • S3: Object storage with 7 storage classes (Standard to Glacier Deep Archive), 99.999999999% durability
  • EBS: Block storage for EC2 with 5 volume types (gp3, gp2, io2, st1, sc1), single AZ attachment
  • EFS: Shared NFS file system, multi-AZ, scales automatically, ideal for shared access
  • Glacier: Long-term archival - Glacier Flexible ($0.0036/GB) vs Deep Archive ($0.00099/GB)

Database:

  • RDS: Managed relational database with 6 engines (Aurora, MySQL, PostgreSQL, MariaDB, Oracle, SQL Server)
  • DynamoDB: NoSQL serverless database, single-digit millisecond latency, auto-scaling
  • ElastiCache: In-memory caching - Redis (persistence, replication) vs Memcached (simple, multi-threaded)
  • Aurora: MySQL/PostgreSQL compatible, 5x faster than RDS MySQL, up to 128 TB storage

Networking:

  • VPC: Virtual Private Cloud with customizable CIDR blocks, subnets, route tables, Security Groups, NACLs
  • Route 53: DNS with 7 routing policies (Simple, Weighted, Latency, Failover, Geolocation, Geoproximity, Multi-value)
  • CloudFront: CDN with 450+ edge locations, caching, OAC for S3 security, signed URLs for restricted content
  • ELB: Load balancing - ALB (Layer 7, HTTP/HTTPS), NLB (Layer 4, TCP/UDP), GLB (Layer 3, network appliances)

Security & Identity:

  • IAM: Identity and Access Management - users, groups, roles, policies with least privilege principle
  • KMS: Key Management Service - envelope encryption, automatic key rotation, $1/key/month
  • GuardDuty: Threat detection analyzing CloudTrail, VPC Flow Logs, DNS logs - 30-day free trial
  • WAF: Web Application Firewall - Layer 7 protection, managed rules, bot control
  • Shield: DDoS protection - Standard (FREE) vs Advanced ($3,000/month)

Monitoring & Management:

  • CloudWatch: Monitoring with metrics, logs, alarms, dashboards - first 10 custom metrics FREE
  • CloudTrail: API call auditing for governance, compliance, risk auditing
  • Config: Resource configuration tracking, compliance checking, change history
  • Systems Manager: Operational insights, automated patching, parameter store

Essential Terminology

High Availability: System continues to function even when components fail (Multi-AZ)

Fault Tolerance: System continues without interruption when components fail (more expensive than HA)

Scalability:

  • Vertical Scaling: Increase instance size (scale up/down)
  • Horizontal Scaling: Add more instances (scale out/in)

Elasticity: Automatically adjust capacity based on demand (Auto Scaling)

Durability: Long-term data protection (S3: 11 9’s = 99.999999999%)

Availability: System uptime percentage (S3 Standard: 99.99% = 52.56 min downtime/year)

Latency: Time delay for data transmission (milliseconds)

Throughput: Amount of data transferred in given time (MB/s, GB/s)

IOPS: Input/Output Operations Per Second (disk performance metric)

Study Approach

  1. Understand Concepts First: Don’t just memorize - understand WHY services are designed this way
  2. Hands-On Practice: Use AWS Free Tier to practice implementing architectures
  3. Compare and Contrast: Know differences (Security Groups vs NACLs, Multi-AZ vs Read Replicas)
  4. Learn Cost Implications: Understand pricing models and cost optimization strategies
  5. Review Architecture Diagrams: Visualize how services interact
  6. Practice Scenarios: Work through real-world use cases and decision-making

Next Steps

Continue to the following sections for detailed coverage of each exam domain:

  • AWS Service Fundamentals: Deep dive into EC2, S3, IAM, RDS, VPC, Lambda, CloudWatch, CloudFront (⭐ START HERE)
  • Secure Architectures: IAM, encryption, security services
  • Resilient Architectures: Multi-AZ, disaster recovery, Auto Scaling
  • High-Performing Architectures: Compute, storage, caching, networking
  • Cost-Optimized Architectures: Cost analysis, optimization strategies