Amazon Bedrock AgentCore Identity
Amazon Web ServicesAmazon 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- 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.
- https://aws.amazon.com/bedrock/agentcore/pricing/ recorded 2026-11-20
Identity is billed at "$0.010 per 1,000 token or API keys requested by the agent", and "is available at no additional charge to customers when they use it through either AgentCore Runtime or AgentCore Gateway".
- https://aws.amazon.com/service-terms/ recorded 2026-11-20
The AWS Service Terms page states that "The Service Terms below govern your use of the Services" and includes service-specific sections for Amazon Bedrock AgentCore, a service agreement rather than a software license.
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/key-features-and-benefits.html recorded 2026-11-20
"The token vault provides security for storing OAuth 2.0 tokens, OAuth client credentials, and API keys with comprehensive encryption at rest and in transit", using customer-managed or service-managed AWS KMS keys.
- https://pypi.org/pypi/bedrock-agentcore/json recorded 2026-11-20
PyPI describes bedrock-agentcore as "An SDK for using Bedrock AgentCore", Apache-2.0, homepage github.com/aws/bedrock-agentcore-sdk-python.
- https://raw.githubusercontent.com/aws/bedrock-agentcore-sdk-python/main/LICENSE.txt recorded 2026-11-20
The repository LICENSE.txt is the Apache License, Version 2.0.
Adoption
not assessedAWS 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.
- https://aws.amazon.com/bedrock/agentcore/pricing/ recorded 2026-11-20
The pricing page prices Identity per token request and gives worked examples but no count of customers, agents or requests.
- https://pypi.org/pypi/bedrock-agentcore/json recorded 2026-11-20
bedrock-agentcore is "An SDK for using Bedrock AgentCore" as a whole, not a package for Identity alone.
Capability
2 medium confidenceAgentCore 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.
- https://aws.amazon.com/about-aws/whats-new/2026/04/amazon-bedrock-agentcore/ recorded 2026-11-20
On-Behalf-Of token exchange is generally available: developers "can exchange an access token for a new scoped-down access token that carries both the original user identity and the agent identity", targeted to one outbound resource.
- https://aws.amazon.com/bedrock/agentcore/pricing/ recorded 2026-11-20
Per-action checks are a separate service: "Each time an agent calls a tool through AgentCore Gateway, Policy checks the action against your rules to determine whether it is allowed or denied", billed as AgentCore Policy, not Identity.
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity-terminology.html recorded 2026-11-20
Defines an agent access token as "An AWS-signed token that contains both workload identity and user identity information, enabling downstream services to make authorization decisions based on both identities", created "through the token exchange process".
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity.html recorded 2026-11-20
"Amazon Bedrock AgentCore Identity is an identity and credential management service designed specifically for AI agents and automated workloads." "Agent identities are implemented as workload identities with specialized attributes".
- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/key-features-and-benefits.html recorded 2026-11-20
"Each agent identity receives a unique ARN"; the service supports the client credentials grant and the authorization code grant, and "All operations are logged with detailed context for security monitoring and compliance reporting".
Verified 2026-11-20