Back to Gap Map Product / UX / Agent identity & authorization

Amazon Bedrock AgentCore Identity

Amazon Web Services
closed / Overall score: n/a

Amazon Bedrock AgentCore Identity registers each AI agent as a workload identity and keeps the OAuth tokens and API keys it needs in a token vault, away from agent code. Agents reach AWS resources and services such as Slack or GitHub as themselves or on a user's behalf, including through an on-behalf-of exchange that scopes a token down to one downstream resource. It is one of AWS's AgentCore services.

Openness

1 high confidence
1.0
license
Proprietary (a managed AWS service used under the AWS Service Terms)
source
closed (the agent identity directory, token vault and credential providers run inside AWS, and no repository publishes them)
clients
Apache-2.0 (aws/bedrock-agentcore-sdk-python publishes the AgentCore SDK, whose @requires_access_token and @requires_api_key decorators call the hosted service)

AgentCore Identity is a managed AWS service billed per token or key request, with no published source or downloadable build. The AgentCore SDK that agents use to fetch credentials is open under Apache-2.0, but it only calls the service and covers every AgentCore service, not Identity alone.

Adoption

not assessed

AWS publishes no customer, agent or request count for AgentCore Identity. The bedrock-agentcore SDK is downloaded for every AgentCore service, from Runtime to Memory, so its downloads cannot be attributed to Identity.

Capability

2 medium confidence
2.0

AgentCore Identity gives each agent an identity of its own and lets it act for a user with a token scoped down to one resource and bound to both identities. It decides who may hold which credential, not whether each tool call may run; that per-action check is sold separately as AgentCore Policy, and Identity has no approval step or signed decision record.

Verified 2026-11-20