Skip to content
IAM Policy Generator

Inline policies belong to one identity, and managed policies are shared

An inline policy is embedded in one IAM user, group or role and deleted with it. A managed policy is a standalone object with its own ARN that attaches to many identities. AWS prefers managed policies when a policy could apply to several entities. Limits differ: 6,144 characters per managed policy, 10,240 for a role's inline total.

Open the workbench ยท All guides

Three identity-based policy kinds differ in who manages them

AWS describes three kinds of identity-based policy. They differ in who manages them, whether permissions can be modified, and how many principals each applies to.

KindManaged byCan you change itAttached to
AWS managedAWSNoMany identities
Customer managedYouYesMany identities
InlineYouYesOne identity

An inline policy lives and dies with its identity

AWS says an inline policy maintains a strict one-to-one relationship between a policy and an identity. It is deleted when you delete the identity. If a policy could apply to more than one entity, AWS says it is better to use a managed policy. AWS's diagram shows two roles that need the same permissions, each with its own copy of an inline policy, which is the pattern that makes review harder: the copies can drift apart.

AWS also notes that you can embed an inline policy when you create the identity or later. Two details from other AWS pages apply to inline policies. Access Analyzer policy validation findings appear for inline user and role policies, but not for inline group policies. And the size limit applies to the sum of all inline policies on an entity, not to each one.

A managed policy changes everywhere it is attached

When you update the permissions of a managed policy, the change applies to every identity it is attached to. For an AWS managed policy, AWS does the update itself, usually when a new service launches. For a customer managed policy you do it, and AWS says a good way to create one is to copy an AWS managed policy and customize it.

This is also the case for the risk: a broad edit to a customer managed policy reaches every role that uses it. To see where a managed policy is attached, run aws iam list-entities-for-policy with the policy ARN, which lists the users, groups and roles it is attached to.

The quotas for the two kinds are different

AWS sets the size of each managed policy at 6,144 characters, not counting white space. For inline policies, the limit is the total size of all inline policies per entity: 2,048 characters for a user, 10,240 for a role and 5,120 for a group. A role can hold as many inline policies as you want as long as the total stays under 10,240 characters.

The count of managed policies per role has a default quota of 20, raised from 10 to 20 in an AWS announcement dated 19 Aug 2026, with a maximum of 25 on request. A user gets 10 by default with a maximum of 20, and a group gets 10. These limits favor several small purpose-built managed policies over one large inline one. The size limits page covers all the numbers.

The workbench reads either form

The workbench reads the JSON of a policy and does not care whether it is inline or managed. It builds identity policies that can be attached either way. The choice is made when you attach the policy, not in its text. The AWS managed policies page lists the policies AWS maintains.

Sources

  1. Managed policies and inline policies, read 16 Nov 2026
  2. IAM and AWS STS quotas, read 16 Nov 2026
  3. AWS IAM now supports 20 managed policies per role by default, read 16 Nov 2026
  4. list-entities-for-policy, AWS CLI, read 16 Nov 2026

Last reviewed 16 Nov 2026.