Chapters0/41 ▾
0 of 41 lessons finished
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 2 · Lesson 2 of 5
Pillar trade-offs and the AWS Well-Architected Tool
1 min read
AWS says you make trade-offs between pillars based on business context. A company may accept lower reliability in a development environment to save money while paying more for a highly reliable production system.
AWS also says security and operational excellence are generally not traded off against the other pillars, so an answer that treats security as a budget lever is wrong.
The AWS Well-Architected Tool is the service for reviewing a workload against these best practices. You define a workload, answer questions for each pillar, and receive an improvement plan with prioritized issues. A high-risk issue is an architectural or operational choice that AWS has found might significantly harm the business.
The tool does not monitor metrics, detect attacks or change resources on its own. AWS Trusted Advisor is different: it runs automated checks on the resources in an account rather than a question-based design review. In short: the Well-Architected Tool reviews design, Amazon CloudWatch watches metrics and alarms, and AWS CloudFormation provisions resources.
Check yourself
1. A solutions team wants to review an existing workload by answering questions for each pillar, then receive an improvement plan with prioritized issues. Which AWS service fits this need?
2. A company lowers the reliability of its development environment to save money, while keeping its mission-critical production system highly reliable at higher cost. How does the Well-Architected Framework view trade-offs like this?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, AWS Well-Architected Framework, An Overview of the AWS Cloud Adoption Framework
AWS Cloud Practitioner cheat sheet: every key fact on one page →