# Attribute-based access control

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

Attribute-based access control grants or denies access by comparing attributes of the caller, the resource and the request, such as tags. In AWS, the attributes are tags on IAM principals and resources, and one policy can serve many projects. It pairs naturally with role sessions, since the attributes can come from the identity provider.

## An example, sourced

AWS documentation describes three IAM roles with the access-project tag key and a policy that allows access when the principal's tag matches the tag on the resource, so new resources are covered without policy edits.

## Why it matters here

Tags let one small policy replace many project-specific policies, which keeps each grant narrow. Tag control then becomes part of the access boundary.

## Related pages

- [Permission set: meaning and an example](/glossary/permission-set/)
- [Custom role: meaning and an example](/glossary/custom-role/)
- [Predefined role: meaning and an example](/glossary/predefined-role/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://leastprivilegeprinciple.com/glossary/attribute-based-access-control/
