# IAM roles for service accounts

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

The earlier Amazon EKS method, often shortened to IRSA, for giving a pod an IAM role. A Kubernetes service account is linked to a role, and the pod's containers use the role's temporary credentials through the AWS SDK. EKS Pod Identity is the newer option.

## An example, sourced

AWS documents that applications in a pod's containers can use an AWS SDK or the AWS CLI to make API requests to AWS services using IAM permissions, and that they must sign requests with AWS credentials. AWS describes IAM roles for service accounts as providing the ability to manage credentials for your applications, similar to the way Amazon EC2 instance profiles provide credentials to EC2 instances. The credentials come through the role instead of a stored key.

## Why it matters here

Clusters often carry both methods. A reviewer has to find which one the agent uses, because the trust policy to read differs: OIDC conditions for one, session tags for the other. Both can coexist in a cluster, and the older one is easier to leave in place by accident.

## Related pages

- [Action group: meaning and an example](/glossary/action-group/)
- [Agent tool: meaning and an example](/glossary/agent-tool/)
- [Agent runtime: meaning and an example](/glossary/agent-runtime/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/iam-roles-for-service-accounts/
