Skip to content
AI Agent Access Control

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

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.

The whole checklist ยท The map

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)
  • "Each EKS Pod Identity association maps a role to a service account in a namespace in the specified cluster." (source)
  • "Create dedicated service accounts for each application, and avoid using" (source)
  • "Agent identity provides a per-agent identity that enables a least-privilege" (source)
  • "Per-agent identities let you scope permissions and audit activity to individual agents." (source)
  • "A system-assigned identity is tied to your container app and is deleted when your container app is deleted." (source)

Sources

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

Last reviewed 16 Nov 2026.