SkarpChapter 3 of 20
Cloud Design Principles and the AWS Well-Architected Framework
Move from ‘what is cloud’ to ‘how do we design in the cloud’ by unpacking the core design principles that guide resilient, efficient architectures on AWS.
From 'What is Cloud?' to 'How Do We Design on AWS?'
Shifting to Design
You know what cloud is and why AWS matters. Now we shift from concepts to design: how do we actually build good architectures in the AWS Cloud?
Two Big Ideas
We focus on: 1) core cloud design principles like scalability, elasticity, fault tolerance, and 2) the AWS Well-Architected Framework that captures AWS best practices.
Exam-Level Skills
For CLF-C02, you must recognize good vs. weak designs in scenarios, connect AWS services to design goals, and understand high availability and cost optimization basics.
Learning Targets
You will be able to list common design principles, define the Well-Architected Framework, summarize its pillars, and relate HA/fault tolerance to AWS choices.
Core Cloud Design Principles on AWS
Why Design Principles?
Design principles help you use cloud as cloud, not as a rented data center. They guide how you build systems that scale, adapt, and survive failures.
Scalability
Scalability is the ability to handle more load by adding resources. In AWS, think more EC2 instances behind a load balancer or letting S3/DynamoDB absorb more traffic.
Elasticity
Elasticity is automatic scale out and scale in as demand changes. Auto Scaling groups that grow at peak and shrink off-peak are classic examples.
Fault Tolerance
Fault tolerance means the system keeps working correctly even when parts fail. Use multiple AZs and redundant components to avoid single points of failure.
High Availability
High availability focuses on staying up and reachable most of the time, with minimal downtime. Multi-AZ and managed services are common HA tools.
AWS Global Infrastructure and Resilient Design
Regions
An AWS Region is a physical location in the world where we cluster data centers. Regions are isolated for fault isolation and regulatory needs.
Availability Zones
An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. AZs are separate failure domains.
Using Multiple AZs
Design for HA by placing EC2 instances in at least two AZs behind a load balancer. If one AZ fails, the other can still serve traffic.
Region-Level Services
Services like S3 and DynamoDB store data redundantly across multiple AZs in a Region, giving built-in durability and availability.
Common Exam Trap
All resources in a single AZ = cheaper but fragile. Multi-AZ designs are the AWS-recommended pattern for production workloads.
Introducing the AWS Well-Architected Framework
What Is the Framework?
The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud.
Why It Exists
It captures AWS and customer experience so you can evaluate and improve architectures instead of reinventing best practices.
Six Pillars (2026)
As of 2026, the pillars are: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability.
Exam-Relevant Use
For CLF-C02, know the purpose of the Framework, the pillars at a high level, and that AWS offers a Well-Architected Tool to review workloads.
Well-Architected Pillars: Operational Excellence, Security, Reliability
Operational Excellence
Operational Excellence is about how you run and monitor systems and improve over time: automation, safe deployments, and good observability.
Security
Security focuses on protecting data and systems. Use least privilege, multiple security layers, and remember the shared responsibility model.
Shared Responsibility Model
Know this verbatim: Security and compliance are shared responsibilities between AWS and the customer.
Reliability
Reliability is about consistent correct operation. Use multi-AZ, health checks, and managed services to minimize downtime and handle failures.
Matching Pillars to Questions
Process/monitoring = Operational Excellence; data protection/access = Security; uptime/failover = Reliability.
Well-Architected Pillars: Performance, Cost Optimization, Sustainability
Performance Efficiency
Performance Efficiency is about using resources efficiently: right instance types, serverless, and managed services to meet performance needs.
Cost Optimization
Cost Optimization focuses on avoiding unnecessary costs: remove idle resources, right-size, and use Auto Scaling and pricing models wisely.
Cost vs Performance
Higher performance can cost more; Well-Architected helps you balance performance with cost rather than always choosing the biggest option.
Sustainability
Sustainability aims to reduce environmental impact: efficient architectures, high utilization, and thoughtful Region choices.
Exam Clues
Response time/throughput = Performance; monthly bill/overprovisioning = Cost; carbon footprint/environment = Sustainability.
Applying Principles: A Simple Web App on AWS
The Scenario
Startup with a marketing site: usually low traffic, big spikes after campaigns. They want good availability but low cost.
Poor Design
Single EC2 instance in one AZ running web and DB, fixed size, no Auto Scaling or backups. Cheap but fragile and hard to operate.
Improved Front End
Host static content on S3 and use CloudFront as a CDN. This boosts performance and availability with minimal admin effort.
Serverless Logic and Data
Use Lambda + API Gateway for dynamic logic and DynamoDB or RDS Multi-AZ for data. These scale automatically and improve reliability.
Monitoring and Costs
Use CloudWatch for metrics/alarms and Cost Explorer/budgets for spending. This supports Operational Excellence and Cost Optimization.
Thought Exercise: Match Decisions to Pillars
Work through this mentally (or jot notes). For each design choice, decide which primary Well-Architected pillar it supports.
- Enabling Multi-Factor Authentication (MFA) for all IAM users
- Which pillar is most directly addressed?
- Hint: Think about protecting access to your AWS account.
- Moving from a single large EC2 instance to an Auto Scaling group of smaller instances across two AZs
- Which pillars are improved? (There can be more than one.)
- Hint: Think about both uptime and cost.
- Using AWS CloudFormation to deploy infrastructure instead of manually clicking in the console
- Which pillar is most directly helped?
- Hint: Consider how this affects repeatability and change management.
- Right-sizing an overpowered database instance to a smaller one after performance testing
- Which pillar is the main driver?
- Hint: The goal is to avoid paying for unused capacity.
- Choosing AWS Lambda over always-on EC2 instances for a low-traffic API
- Which pillars benefit? Consider cost, performance, and environmental impact.
After you answer, compare your reasoning to these reference answers:
- 1: Security
- 2: Reliability and Cost Optimization (and some Performance Efficiency)
- 3: Operational Excellence
- 4: Cost Optimization
- 5: Cost Optimization, Performance Efficiency, and Sustainability
If any of your answers differ, revisit the pillar definitions and think about which goal each decision primarily supports.
Quick Check: Well-Architected Basics
Test your understanding of the AWS Well-Architected Framework and pillars.
Which statement best describes the AWS Well-Architected Framework?
- A checklist of AWS services you must use to be supported by AWS Support
- The AWS pricing model for optimizing EC2 and S3 costs
- The document that describes key concepts, design principles, and best practices for designing and running workloads in the cloud
- A tool that automatically fixes security issues in your AWS account
Show Answer
Answer: C) The document that describes key concepts, design principles, and best practices for designing and running workloads in the cloud
The correct answer is C. By definition, the AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud. It is not a mandatory service checklist, a pricing model, or an auto-fix security tool, though there is an AWS Well-Architected Tool that helps you review workloads against the Framework.
Quiz: High Availability and Cost Optimization
Apply cloud design principles to a simple scenario.
A company runs a critical web application on a single large EC2 instance in one Availability Zone. They want to improve availability and reduce cost during low-traffic periods. Which option best aligns with AWS design principles?
- Upgrade to an even larger EC2 instance in the same Availability Zone to handle more traffic
- Create an Auto Scaling group with smaller EC2 instances across multiple Availability Zones behind a load balancer
- Move the application to a single larger instance in a different Region
- Schedule nightly reboots of the instance to keep it healthy
Show Answer
Answer: B) Create an Auto Scaling group with smaller EC2 instances across multiple Availability Zones behind a load balancer
The correct answer is B. An Auto Scaling group with smaller instances across multiple AZs behind a load balancer improves availability (multi-AZ, no single point of failure) and allows scaling out and in with demand, which helps cost optimization. Upgrading a single instance (A or C) keeps a single point of failure. Nightly reboots (D) do not address availability or cost.
Key Terms Review
Flip through these cards to reinforce core definitions and pillar meanings.
- AWS Region
- An AWS Region is a physical location in the world where we cluster data centers.
- Availability Zone (AZ)
- An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
- AWS Well-Architected Framework
- The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud.
- Scalability
- The ability of a system to handle increased load by adding more resources, such as more EC2 instances or using services that automatically handle more requests.
- Elasticity
- The ability of a system to automatically scale out and scale in as demand changes, growing during peaks and shrinking when demand drops.
- Fault tolerance
- The ability of a system to continue operating correctly even when some components fail, often by using redundancy across multiple Availability Zones.
- High availability
- The ability of a system to remain accessible to users with minimal downtime, often measured as a high percentage of uptime and achieved with multi-AZ designs and failover.
- Cost Optimization pillar
- Well-Architected pillar focused on avoiding unnecessary costs and maximizing value, for example by right-sizing, removing idle resources, and using Auto Scaling.
- Performance Efficiency pillar
- Well-Architected pillar focused on using computing resources efficiently to meet requirements and maintain efficiency as demand changes.
- Operational Excellence pillar
- Well-Architected pillar focused on how you run and monitor systems and continuously improve processes, including automation and observability.
- Security pillar
- Well-Architected pillar focused on protecting data, systems, and assets using controls like IAM, encryption, and network security.
- Reliability pillar
- Well-Architected pillar focused on ensuring a workload performs its intended function correctly and consistently, even when components fail.
- Sustainability pillar
- Well-Architected pillar focused on minimizing the environmental impacts of running cloud workloads by improving efficiency and reducing waste.
Pulling It Together and Next Steps in Your Study Path
Design Mindset Recap
Design with scalability, elasticity, fault tolerance, and high availability in mind. These drive real choices like multi-AZ, Auto Scaling, and managed services.
Framework and Pillars
Remember: the AWS Well-Architected Framework describes key concepts, design principles, and best practices. Know the six pillars and what each focuses on.
Exam Integration
Upcoming diagnostics and mocks will test you with scenarios. Your spaced review and gap guide will reinforce any weak domains automatically.
Self-Check
Without notes, list the six pillars, define scalability vs elasticity, and name one design that improves both Reliability and Cost Optimization.
Key Terms
- AWS Region
- An AWS Region is a physical location in the world where we cluster data centers.
- Elasticity
- The ability of a system to automatically scale out and scale in as demand changes, growing during peaks and shrinking when demand drops.
- Scalability
- The ability of a system to handle increased load by adding more resources, such as more EC2 instances or using services that automatically handle more requests.
- Fault tolerance
- The ability of a system to continue operating correctly even when some components fail, often by using redundancy across multiple Availability Zones.
- Security pillar
- Well-Architected pillar focused on protecting data, systems, and assets using controls like IAM, encryption, and network security.
- Availability Zone
- An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region.
- High availability
- The ability of a system to remain accessible to users with minimal downtime, often measured as a high percentage of uptime and achieved with multi-AZ designs and failover.
- Reliability pillar
- Well-Architected pillar focused on ensuring a workload performs its intended function correctly and consistently, even when components fail.
- Sustainability pillar
- Well-Architected pillar focused on minimizing the environmental impacts of running cloud workloads by improving efficiency and reducing waste.
- Cost Optimization pillar
- Well-Architected pillar focused on avoiding unnecessary costs and maximizing value, for example by right-sizing, removing idle resources, and using Auto Scaling.
- Operational Excellence pillar
- Well-Architected pillar focused on how you run and monitor systems and continuously improve processes, including automation and observability.
- Performance Efficiency pillar
- Well-Architected pillar focused on using computing resources efficiently to meet requirements and maintain efficiency as demand changes.
- AWS Well-Architected Framework
- The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud.
- AWS shared responsibility model
- Security and compliance are shared responsibilities between AWS and the customer.