# Give each agent its own role or service account, not a shared one

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

Check 1 of 30: Give each agent its own role or service account, not a shared one. A shared identity means one agent's access is every agent's access, and logs cannot say which agent acted. A separate identity lets you grant, review and revoke access agent by agent.

## Why it matters

A shared identity means one agent's access is every agent's access, and logs cannot say which agent acted. A separate identity lets you grant, review and revoke access agent by agent.

## How, in each cloud

- **AWS:** Use one Lambda execution role per function, or one EKS Pod Identity association per service account, so each agent maps to its own IAM role.
- **Google Cloud:** Create dedicated service accounts for each application, or use a per-agent agent identity on Agent Runtime.
- **Azure:** Use the per-agent Entra agent identity that Foundry creates, or a system-assigned managed identity that is tied to one container app.

## What the documentation says

- "A Lambda Event Function's execution role is an AWS Identity and Access Management (IAM) role that grants the function permission to access" ([source](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html))
- "Each EKS Pod Identity association maps a role to a service account in a namespace in the specified cluster." ([source](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html))
- "Create dedicated service accounts for each application, and avoid using" ([source](https://cloud.google.com/iam/docs/best-practices-service-accounts))
- "Agent identity provides a per-agent identity that enables a least-privilege" ([source](https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity))
- "Per-agent identities let you scope permissions and audit activity to individual agents." ([source](https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity))
- "A system-assigned identity is tied to your container app and is deleted when your container app is deleted." ([source](https://learn.microsoft.com/en-us/azure/container-apps/managed-identity))

- [Next: Use short-lived role credentials and no long-lived access keys for the agent](/checklist/short-lived-credentials/)

## Related pages

- [Use short-lived role credentials and no long-lived access keys for the agent: the check, and how in AWS, Google Cloud and Azure](/checklist/short-lived-credentials/)
- [Limit who can pass, attach or impersonate the agent's role: the check, and how in AWS, Google Cloud and Azure](/checklist/restrict-who-can-attach-role/)
- [Scope the role's trust to the specific agent, service account or workload: the check, and how in AWS, Google Cloud and Azure](/checklist/scope-trust-to-the-agent/)

## Sources

- docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html: https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html (read 10 Nov 2026)
- docs.aws.amazon.com/eks/latest/userguide/pod-identities.html: https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html (read 10 Nov 2026)
- cloud.google.com/iam/docs/best-practices-service-accounts: https://cloud.google.com/iam/docs/best-practices-service-accounts (read 10 Nov 2026)
- docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident: https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/container-apps/managed-identity: https://learn.microsoft.com/en-us/azure/container-apps/managed-identity (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/own-identity-per-agent/
