AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy
Summary
Provides permissions for operational accounts to diagnose unmanaged nodes by providing Organisation specific permissions required by SSM automation to pull the list of member accounts within a root of an Organisation to trigger cross-account cross-region execution by allowing assuming Execution roles in target account/region.
Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.
Identity
- ARN
arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy- Default version
- v1
- Created
- Last edited
- Services
- organizations, sts
Control-plane actions (3)
By access level: 2 List, 1 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Organizations | 2 of 63 | 2 List; 0 restricted, 0 conditional | organizations:ListChildren, organizations:ListRoots |
| STS | 1 of 16 | 1 Write; 1 restricted, 1 conditional | sts:AssumeRole |
Organizations: 2 actions
- organizations:ListChildren (List)
- organizations:ListRoots (List)
STS: 1 actions
- sts:AssumeRole (Write)
Data-plane actions (0)
By access level: none.
This policy grants no actions in this plane.
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: mixed.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants 1 write, tagging or permissions-management action, short of full control of any service.
Guidance
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Related policies
Same service
- AccessAnalyzerServiceRolePolicy
- AccountAccessManagerServiceRolePolicy
- AIDevOpsOrganizationsAccessPolicy
- AmazonDetectiveOrganizationsAccess
- AmazonDetectiveServiceLinkedRolePolicy
- AmazonDevOpsGuruOrganizationsAccess
- AmazonEKSDashboardConsoleReadOnly
- AmazonEKSDashboardServiceRolePolicy
Same domain
Frequently asked questions
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowReadOnlyAccessOrganization",
"Effect": "Allow",
"Action": [
"organizations:ListRoots",
"organizations:ListChildren"
],
"Resource": "*"
},
{
"Sid": "AllowAssumeDiagnosisExecutionRoleWithinOrg",
"Effect": "Allow",
"Action": "sts:AssumeRole",
"Resource": "arn:aws:iam::*:role/AWS-SSM-DiagnosisExecutionRole*",
"Condition": {
"StringEquals": {
"aws:ResourceOrgId": "${aws:PrincipalOrgId}"
}
}
}
]
}
Version history
Current version v1, edited by AWS on 2024-11-16. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicyCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicyTerraform
resource "aws_iam_role_policy_attachment" "aws_ssm_diagnosisautomation_operationalaccountadministrationrolepolicy" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWS-SSM-DiagnosisAutomation-OperationalAccountAdministrationRolePolicy"),
);Sources
Pending editorial review. No editorial sources are listed yet.