Permissions boundary limiting a user to S3, CloudWatch and EC2
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Permissions boundary limiting a user to S3, CloudWatch and EC2 is an AWS guardrail written in iAM permissions boundaries. Sets the maximum permissions of an IAM user to s3:, cloudwatch: and ec2:*, so the user can never act in other services such as IAM even if an identity policy allows it.
More identity and privilege guardrails ยท About IAM permissions boundaries
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:*",
"cloudwatch:*",
"ec2:*"
],
"Resource": "*"
}
]
}
- Blocks
- Sets the maximum permissions of an IAM user to s3:, cloudwatch: and ec2:*, so the user can never act in other services such as IAM even if an identity policy allows it.
- Breaks
- AWS gives the example of an iam:CreateUser permission policy failing because the boundary does not allow the action. (source)
- Test before applying
- AWS documents that the IAM policy simulator can test IAM permissions boundaries, one boundary at a time. (source)
- Mechanism
- IAM permissions boundaries: A single IAM user or role it is attached to; it does not apply to other principals or to resources.
- Taken from
- provider documentation, provider documentation
What the policy text names
It names 3 actions or patterns: s3:*, cloudwatch:*, ec2:*.
What the source says
"s3:, cloudwatch:, ec2:*" (read 10 Nov 2026).
On what it breaks: "It fails because the permissions boundary does not allow the iam:CreateUser operation."
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
- Permissions boundary limiting a user to S3, CloudWatch and EC2, read 10 Nov 2026
- How to test it first, read 10 Nov 2026
Last reviewed 16 Nov 2026.