AWS’s Well-Architected Agent offers cloud teams two paths to an architecture review: inspect deployed infrastructure or upload infrastructure as code before deployment. It produces prioritized recommendations and remediation instructions, but the preview does not autonomously apply fixes.
In its October 1, 2026 preview announcement, AWS says the agent connects resource configurations, utilization metrics, and application topology with business goals. Findings can come with console instructions, CLI commands, or infrastructure-code changes.
Access requires an AWS Support plan. AWS also warns that generated recommendations can contain errors or incomplete information. The public preview is not an independently validated replacement for architecture review. A bounded pilot gives cloud teams a way to assess whether its findings are verifiable and its proposed changes safe to approve.
Preview Access Requires an AWS Support Plan
AWS says Well-Architected Agent is delivered through AWS Support and is available to customers with an AWS Support plan. The announcement does not specify tier-by-tier eligibility or a separate price for the agent. Teams should confirm access and commercial terms with their AWS Support contacts.
The preview’s access Regions are:
- US East (N. Virginia)
- US East (Ohio)
- US West (Oregon)
These are the Regions where customers access the agent and its recommendations. Workloads can be onboarded from any commercial AWS Region, according to AWS, so they do not have to run in one of those three Regions to be included.
Setup begins in the AWS Well-Architected console. An agent profile defines the accounts, Regions, optimization focus, and goals to analyze. For deployed-environment inspection, customers must also provision customer-managed IAM roles that let the agent read resource configurations, utilization metrics, and application topology. Teams should review that access scope before the first scan.
The Preview Inspects Deployed Resources and Uploaded IaC
For deployed environments, AWS says the agent correlates signals across more than 65 AWS services and evaluates them against Well-Architected best practices. The inputs cover what resources are configured to do, how they are being used, and how they relate within an application.
These inputs provide different kinds of evidence. Configuration alone may reveal a questionable setting; utilization and application context can help establish whether changing it makes sense. The service count, however, does not prove that every feature or architectural dependency receives equivalent scrutiny.
