The Well-Architected agent preview lives in three U.S. regions

A preview with an address

On October 1, 2026, AWS announced a public preview of Well-Architected Agent. The news post says the agent analyzes an AWS environment and returns recommendations on cost, security, performance, and resilience, aligned to goals the customer declares. Access, that post says, is in Northern Virginia, Ohio, and Oregon, while workloads may be onboarded from any commercial region. The profile that holds the advice has a region even when the resources it scans do not. A control plane that lives in one company's rooms is the dependency, and here the rooms are three named regions.when one region is the control plane.

Support plan is where the pages disagree

The news blog and the What's New post say the agent is available to customers with an AWS Support plan. The user-guide release notes, dated with the same preview, say it is available to Business, Enterprise On-Ramp, Enterprise, and Unified Operations. Those are not synonyms for every support tier AWS sells. A reader on a cheaper plan should believe the guide's list until AWS says the blog's broader sentence won. This page will not average them into 'any paying account.'a replica is not a region.

Weekly, and still a draft

The guide says analysis runs on an ongoing schedule and that scheduled recommendations refresh weekly. It says application-level recommendations are a beta format. It says the preview can change. A weekly pass is not a human review that signed a worksheet, and a beta format is not a final finding. The news post adds that the customer must evaluate generative output that may be incomplete. The agent's advice is an input. It is not an acceptance test.the distributed-cloud desk.

What the posts say the agent will hand back

The news post describes three levels: a single resource, an application, and an architecture pattern, with fixes that can include infrastructure-as-code, command-line steps, or a console path. The guide's release notes add runbooks and say a profile can cover more than one account. This brief will not reprint those steps. The fact that matters is that the remediation is generated for the customer's account by a service whose profile sits in one of three regions. InfoQ's October 18 article retells the launch. It does not add a region.Futureweb.

The older tool remains

The news post says customers can still run the existing Well-Architected Tool and define their own lenses. The agent is an addition in preview, not a notice that the manual review closed on October 1. A team that does not want generated fixes still has the worksheet. A team that turns the agent on has accepted the support-plan gate and the weekly cadence. Generated advice is not an advisory in the security-desk sense. Asked directly, How often does the guide say the analysis runs? On a weekly cadence, with recommendations refreshed on that schedule, unlike a one-time architecture review. Application-level recommendations are marked beta in the guide.the advisory is the story.

Sixty-five services is the post's scope line

The news post says the agent analyzes against Well-Architected practices across more than 65 AWS services. That count is AWS's description of coverage, not a list this page will reproduce. A service absent from a later public list would narrow the sentence. Until then, 'more than 65' is the bound the announcement chose. Asked directly, Which support sentence is narrower? The news blog says the agent is delivered by AWS Support and available to customers with an AWS Support plan. The user-guide release notes list Business, Enterprise On-Ramp, Enterprise Support, and Unified Operations. A Developer plan is not in that list.

What would settle the plan gate

A documentation edit that either adds every support tier or deletes the Business-and-above list. A region added or removed from the profile list. An end to the preview that states general availability and a price. InfoQ cannot settle those. Only the AWS pages can, because they are the ones that disagree. Asked directly, When did the preview open? October 1, 2026, in an AWS news post and a What's New item. InfoQ's October 18 piece is a later account of that launch, not a second launch.the paper.

Who is in scope

AWS customers who can open a profile in Northern Virginia, Ohio, or Oregon and who meet the support requirement the guide lists. An account in a commercial region can be scanned, the posts say, without the profile living there. An account outside commercial regions is outside the sentence this page has. Asked directly, Which regions host the profiles? US East in Northern Virginia, US East in Ohio, and US West in Oregon. The posts say workloads can be onboarded from any commercial region. The profile and the resources are not required to share a region.

What stays specific

October 1, 2026, preview, three profile regions, commercial-region scans, a weekly refresh, customer responsibility for generated advice, and a support-plan sentence that is wider on the blog than in the guide. October 18 is when a trade article repeated the launch, not when the preview began. The short answer this page will stand on is this: AWS's October 1, 2026 preview hosts agent profiles in Northern Virginia, Ohio, and Oregon, and it can scan resources in commercial regions. The news posts say customers need an AWS Support plan. The user-guide release notes name Business, Enterprise On-Ramp, Enterprise, and Unified Operations. Recommendations are generated and may be wrong.