EKS Pod Identity
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
An Amazon EKS feature that maps an IAM role to a Kubernetes service account in a namespace, so the pods using that service account receive the role's temporary credentials. It lets two agents in one cluster hold different AWS permissions.
An example, sourced
AWS documents that each EKS Pod Identity association maps a role to a service account in a namespace in a specified cluster. If you run the same application in several clusters, AWS says you can make identical associations in each cluster without modifying the trust policy of the role. AWS states that a container never has access to credentials that are used by other containers in other pods, and that Pod Identity works unchanged with isolated and confidential pods that run in Nitro Sandboxes.
Why it matters here
This is the control that gives each self-hosted agent on EKS its own role. Without an association per service account, agents in a cluster tend to share the node's access. The trust policy on each role should name the service account and namespace.
Related pages
Sources
- https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.