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

```json
{
  "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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html))
- **Test before applying:** AWS documents that the IAM policy simulator can test IAM permissions boundaries, one boundary at a time. ([source](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html))
- **Mechanism:** [IAM permissions boundaries](/mechanisms/permissions-boundary/): A single IAM user or role it is attached to; it does not apply to other principals or to resources.
- **Taken from:** [provider documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html), 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 access](/guardrails/azure-policy-storage-no-shared-key/): Azure, Azure Policy (built-in definitions), identity and privilege
- [Azure Key Vault should use the RBAC permission model](/guardrails/azure-policy-keyvault-use-rbac/): Azure, Azure Policy (built-in definitions), identity and privilege
- [Azure SQL Database should have Microsoft Entra-only authentication enabled](/guardrails/azure-policy-sql-entra-only/): Azure, Azure Policy (built-in definitions), identity and privilege
- [Prevent root credentials management in member accounts](/guardrails/aws-scp-deny-member-root-credentials/): AWS, Service control policies (SCPs), identity and privilege
- [Deny the root user except for S3 bucket policy changes](/guardrails/aws-scp-deny-root-except-s3-bucket-policy/): AWS, Service control policies (SCPs), identity and privilege
- [Deny critical IAM user actions](/guardrails/aws-scp-deny-critical-iam-user-actions/): AWS, Service control policies (SCPs), identity and privilege

## Related pages

- [Permissions boundary for delegated IAM user creation (AWS IAM permissions boundaries)](/guardrails/aws-pb-delegated-user-creation-boundary/)
- [Allowed locations for new resources (Azure Azure Policy)](/guardrails/azure-policy-allowed-locations/)
- [Allowed resource types (Azure Azure Policy)](/guardrails/azure-policy-allowed-resource-types/)

## Sources

- Permissions boundary limiting a user to S3, CloudWatch and EC2: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html (read 10 Nov 2026)
- How to test it first: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_testing-policies.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/guardrails/aws-pb-restrict-user-to-s3-cloudwatch-ec2/
