Deny critical IAM user actions
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Deny critical IAM user actions is an AWS guardrail written in service control policies. Denies creating IAM users, access keys, login profiles and service-specific credentials, and changing the account password policy, unless the caller is a privileged role or carries the IAMUserManagementException tag set to true.
More identity and privilege guardrails ยท About Service control policies
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Deny",
"Action": [
"iam:CreateAccessKey",
"iam:CreateUser",
"iam:UpdateLoginProfile",
"iam:CreateLoginProfile",
"iam:DeleteLoginProfile",
"iam:UpdateAccountPasswordPolicy",
"iam:DeleteAccountPasswordPolicy",
"iam:CreateServiceSpecificCredential"
],
"Resource": "*",
"Condition": {
"ArnNotLike": {
"aws:PrincipalArn": "arn:aws:iam::*:role/[PRIVILEGED_ROLE]"
},
"StringNotLike": {
"aws:PrincipalTag/IAMUserManagementException": "true"
}
}
}
]
}
- Blocks
- Denies creating IAM users, access keys, login profiles and service-specific credentials, and changing the account password policy, unless the caller is a privileged role or carries the IAMUserManagementException tag set to true.
- Breaks
- Anyone outside the named privileged role or tag exception cannot create or rotate IAM user credentials, and the placeholder [PRIVILEGED_ROLE] must be replaced before use. (source)
- Test before applying
- As for every Service control policies guardrail: how to test before enforcing
- Mechanism
- Service control policies (SCPs): IAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.
- Taken from
- open source set, MIT-0 (README states MIT-0; LICENSE file fetched, MIT-0 text, Copyright Amazon.com, Inc.): https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/LICENSE
What the policy text names
It names 8 actions or patterns: iam:CreateAccessKey, iam:CreateUser, iam:UpdateLoginProfile, iam:CreateLoginProfile, iam:DeleteLoginProfile, iam:UpdateAccountPasswordPolicy, iam:DeleteAccountPasswordPolicy, iam:CreateServiceSpecificCredential. Its conditions test aws:PrincipalArn, aws:PrincipalTag/IAMUserManagementException.
What the source says
iam:CreateAccessKey (read 10 Nov 2026).
On what it breaks: "Restrict creation and modification of IAM user profiles, IAM user access keys, service specific credentials such as Amazon Bedrock API keys and account password policy to a privileged role, or principal with the IAMUserManagementException Principal tag set to a value of true."
Related guardrails
- Storage accounts should prevent shared key accessAzure, Azure Policy (built-in definitions), identity and privilege
- Azure Key Vault should use the RBAC permission modelAzure, Azure Policy (built-in definitions), identity and privilege
- Azure SQL Database should have Microsoft Entra-only authentication enabledAzure, Azure Policy (built-in definitions), identity and privilege
- Prevent root credentials management in member accountsAWS, Service control policies (SCPs), identity and privilege
- Deny the root user except for S3 bucket policy changesAWS, Service control policies (SCPs), identity and privilege
- Deny creating or changing IAM federation providersAWS, Service control policies (SCPs), identity and privilege
Related pages
Sources
- Deny critical IAM user actions, read 10 Nov 2026
- What it breaks, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.