# AWS IAM policy types: nine kinds, and each one applies in a different place

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

AWS documents nine policy types: identity-based, resource-based, VPC endpoint, permissions boundary, service control, resource control, access control list, Resource Access Manager share and session policies. Only some grant permissions. The table below, read from AWS documentation on 16 Nov 2026, shows what each is attached to and what it can do.

## Only identity-based, resource-based and ACL policies grant permissions

AWS lists the types from most frequently used to less frequently used. Three of them grant permissions: identity-based policies, resource-based policies and access control lists. The rest set limits. A permissions boundary, an SCP, an RCP and a session policy each state that they do not grant permissions, and a VPC endpoint policy acts as an additional access boundary for traffic that passes through the endpoint.

This split is the quickest way to read an unfamiliar account. A permission has to come from a policy that grants it, and then every limiting policy that applies has to allow it too.

| Policy type | Attached to | Grants permissions | What AWS says it does |
| --- | --- | --- | --- |
| Identity-based | Users, groups, roles | Yes | Controls what actions an identity can perform, on which resources, under what conditions. |
| Resource-based | Resources such as S3 buckets | Yes | Grants the named principal permission to act on that resource, in the same or another account. |
| VPC endpoint | A VPC endpoint | No | Controls which principals can use the endpoint and which resources they can reach through it. |
| Permissions boundary | A user or role | No | Sets the maximum permissions identity-based policies can grant to that entity. |
| Service control policy | Root, OU or account | No | Sets the maximum permissions for IAM users and roles in member accounts. |
| Resource control policy | Root, OU or account | No | Sets the maximum permissions for resources in member accounts. |
| Access control list | A resource | Yes | Controls which principals in other accounts can reach the resource; the only type outside JSON. |
| Resource Access Manager share | Shared resources | Shares resources | Shares resources across accounts without writing a resource-based policy for each. |
| Session policy | A role or federated session | No | Limits what the identity-based policies grant to that session. |

## Identity-based policies come in managed and inline forms

Identity-based policies are either managed or inline. Managed policies are standalone and can be attached to many identities; they are either AWS managed policies, which AWS creates and maintains, or customer managed policies, which you create. Inline policies are embedded in one user, group or role and are deleted with it. The choice between them has its own page: [inline versus managed policies](/inline-vs-managed-policies/).

AWS managed policies are listed on [the managed policies page](/aws-managed-policies/), with the number of actions each one grants on 16 Nov 2026.

## Resource-based policies need a matching identity policy across accounts

AWS says resource-based policies are inline policies and that there are no managed resource-based policies. For cross-account access, naming a principal from another account in the resource-based policy is only half of the trust relationship. When the principal and the resource are in separate accounts, an identity-based policy must also grant the principal access to the resource. If the resource-based policy names a principal in the same account, no additional identity-based policy is required.

IAM itself supports exactly one type of resource-based policy, the role trust policy, which is attached to an IAM role. A role is both an identity and a resource, so it needs a trust policy that says who may assume it and an identity-based policy that says what it may do. [The trust policy page](/aws-trust-policy/) covers the first.

## Limiting policies intersect with what identity policies grant

A permissions boundary limits identity-based policies for a user or role and does not limit a resource-based policy that names the session. An SCP limits the permissions that identity-based and resource-based policies grant to IAM users and roles in member accounts, and an RCP limits the permissions that can be granted on resources in those accounts. Neither SCPs nor RCPs affect the management account of an organization, according to the SCP documentation AWS publishes.

AWS adds three details about the root user. You cannot attach identity-based policies to the root user and you cannot set a permissions boundary for it. You can name the root user as a principal in a resource-based policy or an ACL. And if the account belongs to an organization, SCPs and RCPs for that account affect the root user.

Session policies are passed when you assume a role or create a federated user session through the AWS CLI or API. The session gets the intersection of the session policy and the identity-based policies.

## The workbench builds five of the nine types

The workbench on this site builds and checks identity policies, service control policies, resource control policies, permissions boundaries and role trust policies. It has no builder for the other four types. For a type it does build, it applies the checks that suit that type, for example the document size limit for an SCP or an RCP, which is stated on [the size limits page](/iam-policy-size-limits/).

## Related pages

- [IAM Policy Simulator: What AWS Provides](/iam-policy-simulator/)
- [IAM Access Analyzer: What It Checks and Finds](/iam-access-analyzer/)
- [AWS IAM Best Practices and How to Check Each](/aws-iam-best-practices/)
- [All of them](/guides/)

## Sources

- Policies and permissions in AWS Identity and Access Management: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html (read 16 Nov 2026)
- Service control policies (AWS Organizations): https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html (read 16 Nov 2026)
- Resource control policies (AWS Organizations): https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html (read 16 Nov 2026)
- Policy evaluation logic: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html (read 16 Nov 2026)

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

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