AWS Security ChangesHomeSearch

AWS wellarchitected: AWS WA Agent getting-started: IAM role docs and editorial cleanup

Service: wellarchitected · 2026-11-06 · Documentation low

File: wellarchitected/latest/userguide/agent-getting-started.md · Type: iam

Summary

Replaces the IAM role reference table with a bulleted description of the two console-created roles (ExecutionRoleForWellArchitectedAgent orchestrating discovery and AccessRoleForWellArchitectedAgent granting read-only resource access), adds a prerequisites lead-in sentence, downgrades an 'Important' callout to 'Note', and makes numerous editorial fixes (dash style, 'left navigation', 'propagate' typo).

Security assessment

The IAM role content (read-only access role, discovery execution role) is a reformat of text that already existed in the removed table, so no new permission guidance, least-privilege control, or vulnerability fix is introduced; the rest of the diff is typographic/editorial. Mentions IAM roles but no concrete security remediation.

Evidence

+  * **`AccessRoleForWellArchitectedAgent`** – Grants read-only access to the resources in this account.

Diff

diff --git a/wellarchitected/latest/userguide/agent-getting-started.md b/wellarchitected/latest/userguide/agent-getting-started.md
index 991ad5e..ca36a53 100644
--- a//wellarchitected/latest/userguide/agent-getting-started.md
+++ b//wellarchitected/latest/userguide/agent-getting-started.md
@@ -23 +23 @@ The setup process uses two AWS services:
-  * **IAM** : Create access roles in your workload accounts and update trust policies to establish cross-account access.
+  * **IAM** – Create access roles in your workload accounts and update trust policies to establish cross-account access.
@@ -33,0 +34,2 @@ Once a profile is created and properly configured, AWS WA Agent begins generatin
+Before you set up AWS Well-Architected Agent, make sure that you meet the following requirements:
+
@@ -82 +84 @@ Create an agent profile from the AWS WA Agent console. During profile creation,
-  3. Choose **Agent profiles** in the left-hand navigation.
+  3. Choose **Agent profiles** in the left navigation.
@@ -113 +115 @@ During profile creation, configure the following in **Optimization pillars** :
-  * **Optimization pillar:** Select at least one pillar for AWS WA Agent to analyze: Cost optimization, Security, Resilience, or Performance.
+  * **Optimization pillar** – Select at least one pillar for AWS WA Agent to analyze: Cost optimization, Security, Resilience, or Performance.
@@ -115 +117 @@ During profile creation, configure the following in **Optimization pillars** :
-  * **Goal statement:** Enter at least one plain-text goal statement. Each profile requires a minimum of one goal for AWS WA Agent to generate prioritized recommendations. Goals are editable at any time after creation. For guidance on writing effective goals, see [Goals and personalization in AWS Well-Architected Agent](./agent-goals.html).
+  * **Goal statement** – Enter at least one plain-text goal statement. Each profile requires a minimum of one goal for AWS WA Agent to generate prioritized recommendations. Goals are editable at any time after creation. For guidance on writing effective goals, see [Goals and personalization in AWS Well-Architected Agent](./agent-goals.html).
@@ -126 +128,7 @@ If you chose **The current account** , this section shows **No action needed**.
-The following table describes each role.
+The console creates the following two roles:
+
+  * **`ExecutionRoleForWellArchitectedAgent`** – Orchestrates resource discovery. Assumes the access role to read resources.
+
+  * **`AccessRoleForWellArchitectedAgent`** – Grants read-only access to the resources in this account.
+
+
@@ -128,4 +135,0 @@ The following table describes each role.
-Role name | What it does  
----|---  
-`ExecutionRoleForWellArchitectedAgent` | Orchestrates resource discovery. Assumes the access role to read resources.  
-`AccessRoleForWellArchitectedAgent` | Grants read-only access to the resources in this account.  
@@ -172 +176 @@ To get started with Cost Explorer in your AWS WA Agent profile, choose **Open Co
-After enabling Cost Explorer, it can take up to 24 hours for the data to be available to AWS WA Agent, and resource-level data at daily granularity can take up to 48 hours to propogate. 
+After enabling Cost Explorer, it can take up to 24 hours for the data to be available to AWS WA Agent, and resource-level data at daily granularity can take up to 48 hours to propagate. 
@@ -184 +188 @@ At least one application context is required per profile for AWS WA Agent to gen
-  1. In the left-hand navigation, choose **Agent profiles**. 
+  1. In the left navigation, choose **Agent profiles**. 
@@ -203 +207 @@ After you create your profile, create an IAM access role in each AWS account tha
-###### Important
+###### Note
@@ -244 +248 @@ The execution role ARN format depends on how the role was created:
-  2. In the left-hand navigation, choose **Roles** , then choose **Create role**.
+  2. In the left navigation, choose **Roles** , then choose **Create role**.