On October 1, 2026, AWS stopped pretending the Well-Architected Framework was something you review twice a year. The new AWS Well-Architected Agent — public preview, announced by Channy Yun on the AWS News Blog — scans your deployed accounts and infrastructure-as-code, ranks findings against goals you declare, and ships remediation with each recommendation. AWS frames it as the agent that "evaluates your environment as an experienced cloud architect would." The Register's take was drier: an agent that "recommends cloudy reconfigs," gated behind a paid support plan.

This guide is a launch-week teardown, not a review. Nobody has run this agent in production for longer than a weekend, and we won't pretend otherwise. What we can do — and do here — is read the actual preview documentation: what the agent reads, what it costs to unlock, where its quotas bite, and which teams should ignore it entirely.

TL;DR

  • The Agent is a continuous, goal-ranked audit of up to 100 AWS accounts per profile, refreshing recommendations weekly — versus the Well-Architected Tool, which remains a free, manual, question-driven review you run yourself at milestones.
  • Access is paywalled behind AWS Support at Business+ or higher. Developer and Business tier customers are excluded outright. The cheapest theoretical door in is the Business+ floor: $29/month per account — $348/year — before any percentage-of-spend kicks in.
  • Preview caps are real: 2 profiles and 7 applications on Business+ (10/30 on Enterprise tiers), 30 recommendations per generation run, 5 architecture reviews per day, 25 MB upload ceiling.
  • The IAM surface is a read-only scanning policy — but it reads a lot: configurations, security settings, CloudTrail, Cost Explorer usage, across all commercial Regions.
  • Two honest catches before you get excited: application-level recommendations are explicitly beta, and AWS's own docs carry an Important box telling you to "thoroughly review each recommendation before taking any action." That sentence is the product's real maturity statement.
  • Skip it if you're on Developer/Business support, run fewer than a handful of accounts, or have data-residency constraints that make US-hosted profile regions a problem.

What actually shipped on October 1

Three things landed at once, and most coverage collapsed them into one:

  1. A new service surface — the Agent itself, in the Well-Architected console and the wellarchitected CLI namespace, with new API actions (CreateAgentProfile, CreateAgentGoal, CreateAgentContext, StartAgentRecommendationGeneration, PutAgentRecommendationFeedback, UpdateAgentRecommendationStatus).
  2. A docs restructure — the user guide now opens with an explicit two-track choice: the AI Agent for continuous optimization, the Tool for structured manual reviews. The comparison table below is lifted from that restructure.
  3. The quiet repositioning of Trusted Advisor — the Agent "ingests findings from services such as AWS Trusted Advisor and adds personalization, goal-aligned prioritization, and automation-ready remediation." In other words, the flat checklist era of Trusted Advisor is now the input layer, not the product.

The announcement's three claimed differentiators are consistent across the blog and docs: goal-aligned intelligence (you declare business objectives; recommendations are ranked by impact and effort against them), three-level recommendations (individual resources with dollar impact, consolidated findings scoped to an application, and architecture-level patterns with IaC changes), and optionality in remediation (console walkthrough, updated IaC templates, or CLI commands). AWS also says the agent analyzes best practices "across 65+ AWS services" — note that The AI Economy's launch coverage says "more than 100"; we treat 65+ as the official figure and the discrepancy as a preview-era ambiguity worth pinning down before you write a compliance memo either way.

The 2026 state of the framework: what changed before the agent showed up

The Agent did not appear in a vacuum. The Framework's six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, sustainability — are stable in the current framework edition (2025-02-25), and AWS stated in late 2024 that 100% of best practices had been refreshed at least once since October 2022. What actually moved in 2026 is the lens portfolio — the workload-specific extensions reviewers use — and then, suddenly, the review mechanism itself:

DateWell-Architected changeWhy it matters
Nov 19, 2025Generative AI Lens (updated edition)GenAI workloads got dedicated review guidance before the agent existed
Dec 30, 2025Life Sciences + Telecommunications lensesVertical lenses keep multiplying — the manual review burden keeps growing with them
Jan 27, 2026Financial Services Industry lensSame pattern, regulated vertical
Feb 2, 2026Hybrid Networking + Microsoft workloads lensesAWS reviewing workloads that run someone else's software — a tell about enterprise reality
Jun 10, 2026Agentic AI LensThe framework's first lens for running agents in production — published four months before AWS shipped its own agent
Sep 15, 2026Digital Sovereignty Lens (updated)"Sovereignty is a posture, not a product" — the docs' own line, and directly relevant to where the Agent hosts its profiles
Oct 1, 2026Well-Architected Agent previewThe review process itself becomes a continuously running AWS service

Read that table as one arc: the lens catalog grew faster than any team's capacity to run manual reviews against it. The Agentic AI Lens alone asks teams to review agent systems "reliably, securely, and cost-effectively at scale" — exactly the kind of review that a human architect schedules twice a year and dreads. The Agent is AWS's answer to the review backlog its own lens strategy created. Jill Fariss, Amazon's VP for AWS Support, was blunt about the pain in her launch-week interview with The AI Economy: "Previously, teams had to manually stitch together findings from multiple disconnected tools, then triage hundreds of flat, undifferentiated alerts to figure out what actually mattered. Most of those alerts get missed or ignored because there's no prioritization."

How the agent works: profile, scan, recommend, remediate

The operating model is a four-step loop, and the console walkthrough and API quickstart describe the same flow:

flowchart TB
    SETUP["You: create agent profile
accounts + Regions + pillars + goals"] IAM["Your side: execution role in the scanning account
+ access roles in each workload account"] SCAN["Agent scans: utilization metrics,
resource configurations, application topology
across all commercial Regions"] TA["Ingests existing findings
from AWS Trusted Advisor"] IAC["Optional: upload IaC project
Terraform / CloudFormation / CDK
for pre-deployment review"] RECS["Recommendations at 3 levels:
resource (with dollar impact)
application (beta)
architecture (with IaC changes)"] GOALS["Goals + trade-off analysis rank the list
10 goals per profile, 30 recs per run"] REMED["You pick: console walkthrough,
updated IaC template, or CLI commands"] WEEK["Scheduler re-runs generation
on a weekly cadence"] SETUP --> IAM IAM --> SCAN TA --> RECS SCAN --> RECS IAC --> RECS RECS --> GOALS GOALS --> REMED WEEK --> SCAN