AWS wellarchitected: Restructure AWS WA Agent IAM security headings and add section nav
Summary
Promotes the IAM-related subsections (Execution roles, Cross-account access, Confused deputy prevention, Revoking access, Best practices) from level-6 to level-2 headings, adds a navigation line listing those sections, and reformats list labels from colons to en dashes. No substantive security guidance text is added or changed.
Security assessment
The only added content is a navigation/index line and heading-level changes (e.g. '###### Confused deputy prevention' to '## Confused deputy prevention'); the underlying IAM role-chaining, external ID, and access-revocation guidance is unchanged, so this is a documentation structure edit rather than new or corrected security content.
Evidence
+Execution rolesCross-account accessConfused deputy preventionRevoking accessBest practices
Diff
diff --git a/wellarchitected/latest/userguide/security-iam-agent.md b/wellarchitected/latest/userguide/security-iam-agent.md index 804cb3c..76af176 100644 --- a//wellarchitected/latest/userguide/security-iam-agent.md +++ b//wellarchitected/latest/userguide/security-iam-agent.md @@ -6,0 +7,2 @@ +Execution rolesCross-account accessConfused deputy preventionRevoking accessBest practices + @@ -24 +26 @@ Three principals interact with AWS WA Agent through IAM: -###### Execution roles +## Execution roles @@ -28 +30 @@ When you create a profile, you pass an execution role to AWS WA Agent. The execu -###### Cross-account access +## Cross-account access @@ -32 +34 @@ AWS WA Agent uses IAM role chaining to access resources across multiple accounts - 1. **Admin account (profile account):** Contains the AWS WA Agent profile and the execution role. AWS WA Agent assumes the execution role in this account. + 1. **Admin account (profile account)** – Contains the AWS WA Agent profile and the execution role. AWS WA Agent assumes the execution role in this account. @@ -34 +36 @@ AWS WA Agent uses IAM role chaining to access resources across multiple accounts - 2. **Target accounts:** Each target account contains an access role that the execution role can assume. The access role grants AWS WA Agent read-only permissions to discover and analyze resources. + 2. **Target accounts** – Each target account contains an access role that the execution role can assume. The access role grants AWS WA Agent read-only permissions to discover and analyze resources. @@ -36 +38 @@ AWS WA Agent uses IAM role chaining to access resources across multiple accounts - 3. **Role chain:** AWS WA Agent assumes the execution role, which then assumes the access role in each target account. + 3. **Role chain** – AWS WA Agent assumes the execution role, which then assumes the access role in each target account. @@ -68 +70 @@ Replace `ProfileOwningAccountID` with the AWS account ID where your AWS WA Agent -###### Confused deputy prevention +## Confused deputy prevention @@ -72 +74 @@ AWS WA Agent uses the profile ARN as an external ID in the role assumption chain -###### Revoking access +## Revoking access @@ -76 +78 @@ You retain full control over AWS WA Agent's access at all times. Remove the trus -###### Best practices +## Best practices