Merged from AWS Academy Cloud Foundations + Cloud Architecting. Covers architectural principles, patterns, and design decisions
1. AWS Well-Architected Framework
Framework for designing secure, high-performing, resilient, cost-efficient infrastructure, based on best practices from customer architecture reviews.
______________________________________
| ROOF |
|________________________________________|
| OpEx | Sec | Rel | Perf | Cost | Sust | <- 6 pillars = "pillars" holding up the workload
The Six Pillars
| Pillar |
Focus |
Key Design Principles |
| Operational Excellence |
Run/monitor systems for business value; improve continually |
Operations as code; frequent small reversible changes; refine procedures often; anticipate failure; learn from operational events |
| Security |
Protect systems/data, monitor, respond |
Strong identity foundation; enable traceability; security at all layers; automate security best practices; protect data in transit/at rest; keep people away from data; prepare for security events |
| Reliability |
Recover from failure, mitigate disruption |
Automatically recover from failure; test recovery procedures; scale horizontally; stop guessing capacity; manage change via automation |
| Performance Efficiency |
Use resources efficiently, adapt as tech/demand evolve |
Democratize advanced technologies; go global in minutes; use serverless; experiment often; mechanical sympathy (match tech to task) |
| Cost Optimization |
Eliminate unneeded expense |
Implement Cloud Financial Management; adopt consumption model; measure overall efficiency; stop spending on undifferentiated heavy lifting; analyze & attribute spend |
| Sustainability |
Minimize environmental impact |
Establish sustainability goals; maximize utilization; use efficient hardware/software; reduce downstream impact |
Pillar Review Categories (representative questions)
| Pillar |
Category |
Sample Question |
| Operational Excellence |
Organization / Prepare / Operate / Evolve |
How is workload health understood and managed? |
| Security |
IAM / Detection / Infrastructure protection / Data protection / Incident response |
How are credentials and authentication managed? |
| Reliability |
Foundations / Workload architecture / Change management / Failure management |
How is data backed up? How are component failures withstood? |
| Performance Efficiency |
Selection / Review / Monitoring / Tradeoffs |
How is the best-performing architecture selected? |
| Cost Optimization |
Financial mgmt / Expenditure awareness / Cost-effective resources / Demand & supply / Optimize over time |
Is cost factored into service selection? |
AWS Well-Architected Tool
- Compares an actual workload against the latest AWS best practices.
- Delivers a step-by-step improvement action plan.
- Provides a consistent, repeatable review process across workloads.
2. Shared Responsibility Model
AWS Responsibility: Security OF the Cloud Customer Responsibility: Security IN the Cloud
-------------------------------------------- --------------------------------------------
Physical security (data centers, controlled Customer data
access) Applications, IAM
Hardware/software infrastructure (storage OS / network / firewall configuration
decommissioning, host OS auditing) Client-side data encryption
Network infrastructure (intrusion detection) Server-side encryption
Virtualization infrastructure (instance (file system or data)
isolation) Network traffic protection (encryption,
Global infrastructure (Regions, AZs, edge integrity, identity)
locations)
Responsibility Split by Service Model
| Model |
Customer Flexibility/Responsibility |
AWS Manages |
Examples |
| IaaS |
High — networking, storage, access controls |
Physical infra, virtualization |
EC2, EBS, VPC |
| PaaS |
Focus on code/data |
OS, DB patching, firewall config, DR |
RDS, Elastic Beanstalk, Lambda |
| SaaS |
Minimal — subscription usage only |
Everything else |
Trusted Advisor, AWS Shield, Amazon Chime |
Common Responsibility Examples
| Item |
AWS |
Customer |
| Physical data center security |
✓ |
|
| Virtualization / network isolation between customers |
✓ |
|
| Protecting against Region-wide network outages |
✓ |
|
| OS patches on EC2 |
|
✓ |
| EC2 security group configuration |
|
✓ |
| Application-level configuration |
|
✓ |
| S3 bucket access configuration |
|
✓ |
| Enforcing MFA for user logins |
|
✓ |
| DB engine patches — on RDS |
✓ |
|
| DB engine patches — on EC2-hosted DB |
|
✓ |