AWSManagedAccountManagementAccess

Last Modified

Oct 1, 2026

October 1, 2026 at 08:03 PM UTC

Version

Total Versions

Created

Oct 1, 2026

Actions

Subscribe to updates

Risk

Medium

The same capabilities in a scoped form, resource policy writes, reads across all data, or full access to a whole service. Read from this policy document alone: trust policies, boundaries and SCPs in your account still decide what actually succeeds. How this is assessed

Medium
Can grant itself more permissions
Grants the actions of 2 documented escalation paths, but only on named resources or under a condition. Review that scope before trusting it.
- iam-005iam:PutRolePolicyscoped
  - iam:PutRolePolicy: on arn:*:iam::*:role/managed/*
- iam-009iam:AttachRolePolicyscoped
  - iam:AttachRolePolicy: on arn:*:iam::*:role/managed/*
Use with caution: Check which roles, users or policies fall inside the scope shown above. Within it the escalation works as documented, so keep privileged principals out of it.
Medium
Can take over other users or roles
Grants the actions of 6 documented escalation paths, but only on named resources or under a condition. Review that scope before trusting it.
- iam-012iam:UpdateAssumeRolePolicyscoped
  - iam:UpdateAssumeRolePolicy: on arn:*:iam::*:role/managed/*
- iam-014iam:AttachRolePolicy + sts:AssumeRolescoped
  - iam:AttachRolePolicy: on arn:*:iam::*:role/managed/*
  - sts:AssumeRole: condition aws:ResourceOrgID, on arn:*:iam::*:role/managed/AWSManagedAccountManagementAccessRole
- iam-017iam:PutRolePolicy + sts:AssumeRolescoped
  - iam:PutRolePolicy: on arn:*:iam::*:role/managed/*
  - sts:AssumeRole: condition aws:ResourceOrgID, on arn:*:iam::*:role/managed/AWSManagedAccountManagementAccessRole
- iam-019iam:AttachRolePolicy + iam:UpdateAssumeRolePolicyscoped
  - iam:AttachRolePolicy: on arn:*:iam::*:role/managed/*
  - iam:UpdateAssumeRolePolicy: on arn:*:iam::*:role/managed/*
- iam-021iam:PutRolePolicy + iam:UpdateAssumeRolePolicyscoped
  - iam:PutRolePolicy: on arn:*:iam::*:role/managed/*
  - iam:UpdateAssumeRolePolicy: on arn:*:iam::*:role/managed/*
- sts-001sts:AssumeRolescoped
  - sts:AssumeRole: condition aws:ResourceOrgID, on arn:*:iam::*:role/managed/AWSManagedAccountManagementAccessRole
Use with caution: Check which roles, users or policies fall inside the scope shown above. Within it the escalation works as documented, so keep privileged principals out of it.

Policy Document

View on GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43{
  "PolicyVersion": {
    "Document": {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Effect": "Allow",
          "Action": [
            "iam:AttachRolePolicy",
            "iam:CreateRole",
            "iam:DeleteRole",
            "iam:DeleteRolePermissionsBoundary",
            "iam:DeleteRolePolicy",
            "iam:DetachRolePolicy",
            "iam:GetRole",
            "iam:ListAttachedRolePolicies",
            "iam:ListRolePolicies",
            "iam:PutRolePermissionsBoundary",
            "iam:PutRolePolicy",
            "iam:TagRole",
            "iam:UntagRole",
            "iam:UpdateAssumeRolePolicy",
            "iam:UpdateRole"
          ],
          "Resource": "arn:*:iam::*:role/managed/*"
        },
        {
          "Effect": "Allow",
          "Action": "sts:AssumeRole",
          "Resource": "arn:*:iam::*:role/managed/AWSManagedAccountManagementAccessRole",
          "Condition": {
            "StringEquals": {
              "aws:ResourceOrgID": "${aws:PrincipalOrgID}"
            }
          }
        }
      ]
    },
    "VersionId": "v2",
    "IsDefaultVersion": true,
    "CreateDate": "2026-10-01T19:07:08+00:00"
  }
}