Skip to content
Cloud Governance Tools

Permissions boundary limiting a user to S3, CloudWatch and EC2

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."

Sources

  1. Permissions boundary limiting a user to S3, CloudWatch and EC2, read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.