AWS Well-Architected Tool
A management tool that systematically reviews workloads against AWS best practices across six pillars, visualizing risks that need improvement
Overview
The AWS Well-Architected Tool is a service that helps you review your workloads against AWS architectural best practices organized into six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. It provides a structured questionnaire-based review process that identifies high-risk issues and generates improvement plans with prioritized recommendations.
Background of the Six Pillars and How to Conduct Reviews
The Well-Architected Framework emerged from AWS Solutions Architects' experience reviewing thousands of customer architectures, distilling common patterns of success and failure into six pillars. Each pillar contains design principles and best practices expressed as questions. The review process involves answering these questions for your workload, with each answer indicating whether a best practice is followed, partially followed, or not applicable. The tool calculates risk levels (High Risk, Medium Risk, No Risk) for each pillar based on answers, providing a visual dashboard of your workload's architectural health. Reviews should involve the team that builds and operates the workload, as they have the context to accurately answer questions. A typical initial review takes 2-4 hours and surfaces the most critical architectural risks.
Custom Lenses and Milestones for Continuous Improvement
Beyond the standard six pillars, Custom Lenses enable organizations to codify their own architectural standards and review criteria. Industry-specific lenses (Financial Services, Healthcare, SaaS) are available from AWS, and organizations can create internal lenses reflecting their specific requirements such as data residency rules, approved service lists, or internal security standards. Milestones capture the state of a workload review at a point in time, enabling tracking of improvement over successive reviews. By saving milestones after each review cycle, teams can demonstrate progress in addressing identified risks. The improvement plan generated after each review prioritizes recommendations by risk level and effort, providing a clear roadmap for architectural improvements.
Operational Design to Prevent Review Fatigue
The most common failure mode for Well-Architected reviews is treating them as one-time compliance exercises rather than ongoing improvement tools. To prevent this, integrate reviews into existing operational rhythms: conduct reviews quarterly or after significant architectural changes, assign ownership of identified risks to specific team members with deadlines, and track improvement plan completion in existing project management tools. Trusted Advisor integration automatically surfaces some Well-Architected findings without manual review. For organizations with many workloads, prioritize reviews for business-critical and high-risk workloads first. The Well-Architected Tool API enables programmatic review creation and status tracking, supporting automation of review scheduling and progress reporting. Sharing reviews across accounts enables central architecture teams to maintain visibility into workload health across the organization.