AWS announced the public preview of AWS Well-Architected Agent on October 1, 2026. AWS says the service analyzes utilization metrics, resource configurations, and application topology, then prioritizes recommendations against customers’ goals for cost optimization, performance, resilience, and security.
What the Agent analyzes and recommends
AWS says the Agent assesses practices across 65+ AWS services. It organizes findings at three levels:
| Recommendation scope | AWS-described output |
| Individual resource | Findings about a specific resource |
| Application | Findings consolidated across resources in an application |
| Architecture | Architectural patterns and designs, including Infrastructure as Code (IaC) changes |
The Agent uses customer-declared goals to prioritize recommendations, with impact and effort also informing that prioritization. Its dashboard includes goals, recommendation categories, tabs, and filters for reviewing findings.
Setting up a profile
Customers create a profile in the AWS Well-Architected console, choose accounts or Regions and optimization pillars, set goals, and add application context as needed. They also configure customer-managed IAM roles. AWS says initial resource and application recommendations are generated within 24 hours after profile creation.
For architecture reviews before deployment, customers can upload projects built with Terraform, AWS CloudFormation, or AWS CDK. Infrastructure as Code (IaC) means defining cloud resources in files that can be reviewed and changed as part of a project.
Implementation guidance and the existing review tool
AWS describes several ways to act on findings: console walkthroughs, updated IaC changes, or AWS CLI commands. The guidance gives teams paths for carrying out remediation; AWS’s announcement does not describe the Agent applying changes autonomously.
The Agent is separate from AWS Well-Architected Tool, which remains available for manual architecture evaluations using user-defined lenses. The preview is intended to generate contextual, prioritized recommendations; the existing Tool supports a manual review workflow.
Preview access and customer review
AWS lists preview access in US East (N. Virginia), US East (Ohio), and US West (Oregon). Workloads from any AWS commercial Region can be onboarded. An AWS Support plan and customer-managed IAM roles are required.
AWS warns that AI-generated recommendations may contain errors or incomplete information. Customers are responsible for evaluating recommendations in their own context and applying appropriate oversight and safeguards.
