# IAM policy size limits range from 2,048 to 10,240 characters, depending on the policy type

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

AWS caps a managed policy at 6,144 characters, a user's inline policies at 2,048, a role's at 10,240 and a group's at 5,120, none counting white space. Organizations allows 10,240 characters for an SCP and 5,120 for an RCP. These figures come from the AWS quotas pages read on 16 Nov 2026.

## IAM sets size limits per policy and per entity, and they cannot be raised

AWS states that you cannot request an increase for the character limits. They are listed under fixed limits on the IAM quotas page. AWS says IAM does not count white space when it measures a policy against the managed and inline limits.

| What is limited | Limit | Note |
| --- | --- | --- |
| Each managed policy | 6,144 characters | Stated for managed policies |
| Inline policies on a user | 2,048 characters in total | Sum of all inline policies on that user |
| Inline policies on a role | 10,240 characters in total | Sum of all inline policies on that role |
| Inline policies on a group | 5,120 characters in total | Sum of all inline policies on that group |

## Counts of attached policies are quotas that can be raised

Other IAM limits are counts, and AWS lists a default quota and a maximum quota for each.

| Item | Default | Maximum |
| --- | --- | --- |
| Managed policies per role | 20 | 25 |
| Managed policies per user | 10 | 20 |
| Managed policies per group | 10 | 10 |
| Customer managed policies per account | 1,500 | 10,000 |
| Role trust policy length (characters) | 2,048 | 8,192 |
| Roles per account | 1,000 | 10,000 |
| Groups per account | 300 | 500 |

## The managed policies per role default was raised from 10 to 20

AWS announced on 19 Aug 2026 that IAM increased the default quota for managed policies per role from 10 to 20. AWS says the higher default reduces the need for Service Quotas requests when you separate permissions into purpose-specific policies or onboard partner products that need extra managed policies, and that you can request up to 25. The change applies automatically to all roles and covers commercial Regions, AWS GovCloud (US) and China Regions.

A role with 20 managed policies of 6,144 characters each could hold up to 122,880 characters of managed policy text, against 10,240 characters for inline policies. The two figures are separate limits, and a role can use both kinds of policy.

## Organizations sets its own limits for SCPs and RCPs

The AWS Organizations quotas page gives separate numbers for the organization policy types, and the first two are the ones this workbench checks.

| Policy type | Maximum document size | Policies per organization | Attachable per root, OU or account |
| --- | --- | --- | --- |
| Service control policy | 10,240 characters | 10,000 | 10 |
| Resource control policy | 5,120 characters | 2,000 | 5, including the automatic RCPFullAWSAccess |
| Declarative policy | 10,000 characters | 1,000 | 10 |
| Backup policy | 10,000 characters | 1,000 | 10 |
| Tag policy | 10,000 characters | 1,000 | 10 |
| AI services opt-out policy | 2,500 characters | 1,000 | 5 |

## White space is counted differently depending on how you save

AWS notes for Organizations that if you save a policy in the console, extra white space between JSON elements and outside quotation marks is removed and not counted. If you save with an SDK or the CLI, the policy is saved exactly as you provided it and no characters are removed. A policy that fits in the console may fail through the CLI for that reason.

The workbench counts characters with all white space removed, the way the IAM quotas page does, and reports an SCP over 10,240 and an RCP over 5,120 as high-severity findings. It removes every white space character, including those inside strings, so a count close to a limit should be confirmed in the target service. Other Organizations limits include 2,000 OUs in an organization and OU nesting of five levels under the root. See [the evaluation logic page](/iam-policy-evaluation-logic/) for how SCPs combine with other policies.

## Related pages

- [AWS IAM Actions: Names, Prefixes and Counts](/aws-iam-actions/)
- [IAM Access Levels: List, Read, Write, Tagging, Permissions](/iam-access-levels/)
- [IAM Policy: What It Is and How to Read One](/iam-policy/)
- [All of them](/guides/)

## Sources

- IAM and AWS STS quotas: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-quotas.html (read 16 Nov 2026)
- Quotas and service limits for AWS Organizations: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_reference_limits.html (read 16 Nov 2026)
- AWS IAM now supports 20 managed policies per role by default: https://aws.amazon.com/about-aws/whats-new/2026/08/aws-iam-quota-increase/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/iam-policy-size-limits/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
