AWS Well-Architected Tool & Operational Governance

Well-Architected turns architecture review into a repeatable process

The AWS Well-Architected Framework provides a structured set of questions and best practices for evaluating architecture decisions. Its six pillars are Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization and Sustainability. The point is not to maximize every pillar independently; workload context creates trade-offs. The framework gives teams a common vocabulary for exposing those trade-offs and deciding where risk is acceptable or needs improvement.

AWS Well-Architected Tool (AWS WA Tool) is the AWS service that records and supports this review process. A workload represents a set of components that delivers business value and can span resources or accounts. Teams document workload characteristics and answer lens questions, then use the resulting recommendations and risks to guide an improvement backlog. It is therefore a governance workflow rather than a monitoring agent that automatically inspects every property of running infrastructure.

Lenses, HRIs and MRIs turn broad best practices into prioritized review findings

A lens is a set of questions and best practices applied to a workload. The AWS Well-Architected Framework Lens provides the general AWS review, while additional AWS or custom lenses can focus on particular technologies or organizational requirements. This lets a team apply one consistent workload record to both broad architectural governance and more specialized review criteria.

Based on the documented answers, AWS WA Tool can identify high risk issues (HRIs) and medium risk issues (MRIs). These are review findings about architectural and operational choices, not automated proof that an incident will occur. The improvement plan connects identified risks to recommended actions, and teams should prioritize those actions using business impact, engineering constraints and the workload's lifecycle. A documented reason for accepting a risk can be as important for governance as blindly checking a box.

• Framework = best-practice review methodology; WA Tool = service that records workloads and review results.
• Lens = a set of review questions/best practices applied consistently to a workload.
• HRI/MRI = identified architectural risk level based on review answers, not a live CloudWatch alarm severity.

Milestones preserve review state as the architecture evolves

A milestone records the state of a workload at a particular point in time. AWS recommends saving milestones as meaningful improvements or lifecycle transitions occur so teams can compare architectural risk over time. A milestone is valuable because a live workload record continues to change; the saved snapshot provides evidence of what the review looked like at a release, go-live decision or governance checkpoint.

Well-Architected governance becomes strongest when review findings connect back to operational evidence. CloudWatch metrics and logs can test assumptions about reliability or performance, Trusted Advisor recommendations can contribute supporting findings, and organizational standards can be represented in custom review practices. The WA Tool does not replace those services; it supplies the architecture-review layer that helps decision makers turn evidence into a prioritized improvement process.