Deny creating or changing IAM federation providers
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Deny creating or changing IAM federation providers is an AWS guardrail written in service control policies. Denies creating, updating or deleting IAM SAML and OpenID Connect identity providers unless the caller is the privileged role. Copied from a licensed open source set and read on 10 Nov 2026.
More identity and privilege guardrails ยท About Service control policies
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Deny",
"Action": [
"iam:CreateOpenIDConnectProvider",
"iam:CreateSAMLProvider",
"iam:DeleteOpenIDConnectProvider",
"iam:DeleteSAMLProvider",
"iam:UpdateOpenIDConnectProviderThumbprint",
"iam:UpdateSAMLProvider"
],
"Resource": "*",
"Condition": {
"ArnNotLike": {
"aws:PrincipalARN": "arn:aws:iam::${Account}:role/[PRIVILEGED_ROLE]"
}
}
}
]
}
- Blocks
- Denies creating, updating or deleting IAM SAML and OpenID Connect identity providers unless the caller is the privileged role.
- Breaks
- Teams that manage their own identity providers in member accounts are blocked unless they use the privileged role; the README says it is usually paired with the critical IAM user actions policy. (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 6 actions or patterns: iam:CreateOpenIDConnectProvider, iam:CreateSAMLProvider, iam:DeleteOpenIDConnectProvider, iam:DeleteSAMLProvider, iam:UpdateOpenIDConnectProviderThumbprint, iam:UpdateSAMLProvider. Its conditions test aws:PrincipalARN.
What the source says
iam:CreateSAMLProvider (read 10 Nov 2026).
On what it breaks: "Restrict the creation of new and modification of existing IAM federation, this policy is usually used in conjunction with"
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 critical IAM user actionsAWS, Service control policies (SCPs), identity and privilege
Related pages
Sources
- Deny creating or changing IAM federation providers, 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.