Module Objective: Define cloud architecture, apply the AWS Well-Architected Framework to evaluate a design, and describe best practices for building solutions on AWS.
Review module: This module reviews concepts from AWS Academy Cloud Foundations Modules 3 and 9 at a higher level before the course moves into new material.
What Is Cloud Architecting?
Cloud architecting is the practice of designing systems that use cloud resources to meet business and technical requirements — balancing functionality, cost, performance, security, and reliability rather than optimizing any single dimension in isolation.
Unlike traditional on-premises architecture, cloud architecture design decisions can be revisited more cheaply and frequently, since resources are provisioned on demand rather than purchased upfront.
The AWS Well-Architected Framework
The Well-Architected Framework's six pillars — Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability — provide the lens this entire course uses to evaluate architectural decisions.
Each subsequent module that adds a new architectural layer will implicitly ask: does this design choice hold up under each of the six pillars?
| Pillar | Central Question |
|---|---|
| Operational Excellence | Can we run and improve this system with minimal manual effort? |
| Security | Is data and access protected at every layer? |
| Reliability | Will this recover automatically from failure and meet demand? |
| Performance Efficiency | Are we using the right resources, efficiently, as demand changes? |
| Cost Optimization | Are we avoiding unnecessary spend? |
| Sustainability | Are we minimizing environmental impact? |
Best Practices for Building Solutions on AWS
AWS has published a set of recurring best practices, distilled from operating experience across millions of customer workloads, that show up repeatedly throughout this course.
| Practice | What It Means |
|---|---|
| Design for failure | Assume any component can fail, and design so that failure doesn't take down the whole system |
| Decouple components | Reduce dependencies between components so they can scale and fail independently |
| Implement elasticity | Scale resources up and down automatically to match actual demand |
| Think parallel | Design workloads to run across many resources concurrently rather than one large resource |
AWS Global Infrastructure
Architectural decisions about Regions, Availability Zones, and edge locations — introduced in AWS Academy Cloud Foundations — remain foundational here: nearly every layer added in Modules 3–8 has to be placed somewhere in that physical hierarchy.
Design Patterns and Architectural Options
A design pattern is a reusable, proven approach to a recurring architectural problem — for example, using a queue to decouple two components, or using a load balancer with multiple targets for availability.
This course builds a working vocabulary of AWS design patterns module by module, so that by Module 15 they can be recognized and applied quickly under exam conditions.
Key Terms for Module 2
- cloud architecture
- The practice of designing systems using cloud resources to meet business and technical requirements
- Well-Architected Framework
- AWS's six-pillar framework for evaluating cloud architectures
- design pattern
- A reusable, proven approach to a recurring architectural problem
- design for failure
- The best practice of assuming any component can fail and designing so failure doesn't cascade
Review Questions
- How does cloud architecting differ from simply provisioning individual AWS services?
- What question does each of the six Well-Architected pillars ask about a design?
- What does "design for failure" mean in practice, and which later module explores it in depth?
- Why does this course build a vocabulary of design patterns rather than teaching services in isolation?