Everything below comes from public sources. The company has not reviewed this profile. Data last verified: 16 October 2026. Status labels are defined in the methodology. About this record.
Publisher interest: HumanAudit Inc., which publishes this site, sells governance documentation and plans NHI governance packs, including an RFP kit that does not name, rank or recommend any vendor. It builds and sells no NHI scanner and no NHI discovery, monitoring or security tool.
At a glance
Scroll sideways to see all columns.
| Ownership | Amazon Web ServicesVerifiedSource: AWS documentation: Amazon Bedrock AgentCore Identity (Official product documentation). |
|---|---|
| Product status | Part of Amazon Bedrock AgentCore: preview July 2025, generally available October 2025VerifiedSource: AWS documentation: Amazon Bedrock AgentCore release notes (Official product documentation). Months are from the AWS release notes, which give no exact days. |
| Agent identity | Each agent identity is a workload identity with a unique ARN, held in a central directoryVerifiedSource: AWS documentation: Features of AgentCore Identity (Official product documentation). |
| Token vault | Stores OAuth 2.0 tokens, OAuth client credentials and API keys, encrypted with AWS KMS keys; access requires proof of workload identityVerifiedSource: AWS documentation: Features of AgentCore Identity (Official product documentation). |
| On-behalf-of exchange | Generally available 30 April 2026 in 14 AWS RegionsVerifiedSource: AWS What's New: Amazon Bedrock AgentCore Identity now supports On-Behalf-Of (OBO) token exchange (Official company announcement). |
| Exchange standards | RFC 8693 token exchange or RFC 7523 for custom OAuth 2.0 providers; a Microsoft provider type is also documentedVerifiedSource: AWS documentation: On-behalf-of token exchange (Official product documentation). |
| Built-in credential providers | Google, GitHub, Slack, Salesforce and Atlassian (Jira), plus configurable OAuth 2.0 providersVerifiedSource: AWS documentation: Features of AgentCore Identity (Official product documentation). |
| Recent additions | Secrets Manager references (June 2026) and a hosted Consent Portal (September 2026)VerifiedSource: AWS documentation: Amazon Bedrock AgentCore release notes (Official product documentation). |
Source audit: AI research assistants checked the facts in this profile line by line against public sources on 16 October 2026. Akshay Dubey, the editor, is accountable for publication. Each fact carries a label for the kind of evidence behind it. What could not be confirmed is listed under What we could not verify.
What changed recently
- 13 Oct 2026: AWS Agent Registry added custom metadata fields on agent records, such as team ownership, data classification and review status, searchable through the console, CLI, SDKs and MCP endpoint
- Sep 2026: Consent Portal for AgentCore Identity released
- Aug 2026: AWS Agent Registry generally available, with auto-detection through AWS Organizations
- Jun 2026: Identity credential providers can reference existing AWS Secrets Manager secrets
Categories and identity types
Scroll sideways to see all columns.
| Categories | Agent identity (platform), Workload identity, Credential vault |
|---|---|
| Identity and credential types (as the company describes them) | AI agents (workload identities), MCP servers, OAuth tokens and API keys |
Capability evidence is in the capability matrix below.
Funding history
No funding round is recorded for this entry. For acquired companies, public companies and products of larger companies, see ownership above.
Disclosed investors: Not applicableVerifiedSource: AWS documentation: Amazon Bedrock AgentCore Identity (Official product documentation).
Product of AWS; funding not applicable.
What AWS documents
AgentCore Identity provides centralised agent identity management: each agent identity receives a unique ARN for precise access control. Its token vault stores OAuth 2.0 tokens, client credentials and API keys, encrypted at rest and in transit, and releases them only to authorised agents that present verifiable proof of workload identity, validating every request independently. With on-behalf-of token exchange, generally available since April 2026, an agent exchanges a user's access token for a new, scoped-down token targeted at a specific downstream resource. That token carries both the original user identity and the agent identity, granting just-in-time, least-privilege access without additional user consent prompts. The same mechanism is available to MCP servers.
Why it matters for accountability
A token that names both the user and the agent lets downstream systems log that an agent acted, and for whom. Combined with workload identities and a vault, the design is intended to replace the pattern of agents running with a person's long-lived credentials.
Where it sits in the market
For teams building agents on AWS, AgentCore Identity is AWS's own identity layer for agents, comparable in role to Microsoft Entra Agent ID for Microsoft-centric estates.
Strengths, on the evidence
- Delegation that preserves both user and agent identity.
- Vaulted credentials released only on proof of workload identity.
- Broad regional availability.
Gaps and what we do not know
- Ownership or sponsor assignment for agents not documented in sources reviewed.
- Covers agents built on AWS; cross-cloud governance needs other tools.
- Quotas and token lifetimes are set out in AWS documentation and were not assessed for this profile.
- AWS documents that operations are logged. Public documentation reviewed for this profile did not establish the logging detail or any detection features.
What AgentCore says about the market
Cloud providers are standardising delegated agent identity. Governance programmes can now require that agents act through on-behalf-of tokens, not borrowed credentials, as a testable control.
Common questions
- What does Amazon Bedrock AgentCore Identity do for non-human identity?
- AgentCore Identity addresses how an agent built on AWS proves who it is and obtains credentials for other systems. It replaces embedded long-lived secrets with a workload identity, a vault and short-lived delegated tokens. It is an identity issuer and credential broker, not a discovery or governance product. (Our analysis of public documentation.)
- Who owns Amazon Bedrock AgentCore Identity?
- Amazon Web Services.
- Does Amazon Bedrock AgentCore Identity cover AI agents?
- Evidence status: Documented by vendor. The service is described as identity and credential management designed for AI agents and automated workloads.
- Who are Amazon Bedrock AgentCore Identity's competitors?
- In our analysis of product scope: Microsoft Entra (Workload ID / Agent ID), Google Cloud IAM / Workload Identity Federation. See Competitors and alternatives.
Timeline
Scroll sideways to see all columns.
| Date | Event | Source |
|---|---|---|
| 13 Oct 2026 | AWS Agent Registry added custom metadata fields on agent records, such as team ownership, data classification and review status, searchable through the console, CLI, SDKs and MCP endpoint | AWS What's New: AWS Agent Registry now supports custom metadata for registry records |
| Sep 2026 | Consent Portal for AgentCore Identity released | AWS documentation: Amazon Bedrock AgentCore release notes |
| Aug 2026 | AWS Agent Registry generally available, with auto-detection through AWS Organizations | AWS documentation: Amazon Bedrock AgentCore release notes |
| Jun 2026 | Identity credential providers can reference existing AWS Secrets Manager secrets | AWS documentation: Amazon Bedrock AgentCore release notes |
| 30 Apr 2026 | On-behalf-of token exchange generally available in 14 Regions | AWS What's New: Amazon Bedrock AgentCore Identity now supports On-Behalf-Of (OBO) token exchange |
| Apr 2026 | Identity, Gateway and Runtime gain egress to resources in customer VPCs | AWS documentation: Amazon Bedrock AgentCore release notes |
| Mar 2026 | AgentCore Policy generally available in thirteen Regions | AWS documentation: Amazon Bedrock AgentCore release notes |
| Oct 2025 | Amazon Bedrock AgentCore generally available in nine AWS Regions | AWS documentation: Amazon Bedrock AgentCore release notes |
| Jul 2025 | Amazon Bedrock AgentCore, including Identity, released in preview | AWS documentation: Amazon Bedrock AgentCore release notes |
Leadership
No named leadership was recorded for this entry from the sources reviewed. For a product of a larger company, see the parent company.
Products
Amazon Bedrock AgentCore Identity
An AWS identity and credential management service for AI agents and automated workloads. It provides a directory of workload identities, a token vault, and OAuth 2.0 flows so agents can reach AWS resources and third-party services. It works with AgentCore Runtime and AgentCore Gateway. [source]
Token vault and credential providers
Stores OAuth 2.0 tokens, OAuth client credentials and API keys, encrypted with customer-managed or service-managed KMS keys. Credentials are released only to agents that prove their workload identity. Built-in providers cover Google, GitHub, Slack, Salesforce and Atlassian. [source]
On-behalf-of token exchange
Lets an agent or MCP server swap an inbound user access token for a scoped token aimed at a downstream resource server, without a further consent prompt. The new token carries the agent's and the caller's identities. Generally available since 30 April 2026. [source]
Consent Portal
A hosted portal, added in September 2026, where end users grant consent for an agent to access resources on their behalf. [source]
Capability matrix
This matrix records what public evidence shows. It is not a score. Documented by vendor means the company's own documentation or product pages describe the capability; it is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation, which is different from saying the product lacks the capability.
11 documented by the vendor, 0 independently reported, 10 not publicly verified.
Scroll sideways to see all columns.
| Capability | Evidence status | What the evidence says |
|---|---|---|
| NHI discovery | Not publicly verified | The directory holds identities that are created in it. Release notes mention auto-detection in the separate AWS Agent Registry, which is outside the scope of this profile. |
| NHI inventory | Documented by vendor | Documentation describes a unified directory as the single source of truth for agent and workload identities in an organisation. [source] |
| Ownership assignment | Not publicly verified | We did not find public documentation of a named owner or sponsor field for agent identities. |
| Attribution to humans | Documented by vendor | On-behalf-of tokens carry both the agent identity and the original caller's identity. [source] |
| Access analysis | Not publicly verified | Public documentation reviewed for this profile did not establish this capability. |
| Authorization policy | Not publicly verified | An inbound JWT authorizer is listed in the Identity documentation. AgentCore Policy is a separate component and was not reviewed for this profile. |
| Least privilege | Documented by vendor | On-behalf-of exchange issues a scoped-down token aimed at one downstream resource, described by AWS as just-in-time, least-privilege access. [source] |
| Lifecycle management | Documented by vendor | Creating, managing and organising workload identities is documented. Automated review or retirement is not described. [source] |
| Credential rotation | Not publicly verified | Public documentation reviewed for this profile did not establish this capability. |
| Secrets management | Documented by vendor | The token vault stores OAuth tokens, client credentials and API keys under KMS encryption. Since June 2026 providers can reference AWS Secrets Manager secrets. [source] |
| Certificate management | Not publicly verified | Public documentation reviewed for this profile did not establish this capability. |
| Service accounts | Not publicly verified | Public documentation reviewed for this profile did not establish this capability. |
| API keys | Documented by vendor | API keys can be stored in the token vault and released to authorised agents. [source] |
| OAuth apps and tokens | Documented by vendor | OAuth 2.0 client credentials and authorization code flows are supported, with built-in providers for several SaaS services. [source] |
| Workload identity | Documented by vendor | Agent identities are implemented as workload identities, each with a unique ARN. [source] |
| Cloud identity | Documented by vendor | Workload identities are AWS resources with ARNs. The wider AWS IAM service was not reviewed for this profile. [source] |
| AI agents | Documented by vendor | The service is described as identity and credential management designed for AI agents and automated workloads. [source] |
| Agent governance | Not publicly verified | Agent identity and delegated access are documented. We did not find public documentation of ownership, review or approval workflows in AgentCore Identity. |
| Monitoring and detection | Not publicly verified | Logging of operations is documented. We did not find public documentation of detection features in AgentCore Identity. |
| Remediation | Not publicly verified | Public documentation reviewed for this profile did not establish this capability. |
| Audit evidence | Documented by vendor | Documentation states that all operations are logged with detailed context for security monitoring and compliance reporting. [source] |
Customers
No named customers were found in the public sources reviewed. That does not mean there are none.
Positioning: claim and analysis
What the company says: AWS describes AgentCore Identity as an identity and credential management service designed for AI agents and automated workloads, letting agents act on behalf of users while keeping security controls and audit trails. [source]
What NHI problem it addresses (our analysis): AgentCore Identity addresses how an agent built on AWS proves who it is and obtains credentials for other systems. It replaces embedded long-lived secrets with a workload identity, a vault and short-lived delegated tokens. It is an identity issuer and credential broker, not a discovery or governance product.
Where the evidence is strongest (our analysis): Delegated tokens that name both user and agent give downstream systems a basis for attribution. Vault access is tied to proof of workload identity. The exchange follows published standards (RFC 8693 and RFC 7523), and release notes show steady additions through 2026. All of this is vendor documentation and was not independently tested.
What public information does not establish:
- Public documentation reviewed for this profile did not establish a named owner or sponsor for each agent identity.
- Public documentation reviewed for this profile did not establish discovery of agents or credentials created outside AgentCore.
- Public documentation reviewed for this profile did not establish credential rotation, certificate management or detection features within AgentCore Identity.
- AgentCore Policy, AWS Agent Registry and AWS IAM are outside the scope of this profile; some governance functions may sit there.
Competitors and alternatives
These groupings are our analysis of overlapping product scope. They are not rankings, and order carries no meaning.
Scroll sideways to see all columns.
| Relationship | Company or approach | Why it overlaps |
|---|---|---|
| Direct competitor | Microsoft Entra (Workload ID / Agent ID) | cloud provider agent identity service |
| Direct competitor | Google Cloud IAM / Workload Identity Federation | cloud provider workload identity service |
| Adjacent | Auth0 for AI Agents | token storage and delegated access for agents from an identity vendor |
| Adjacent | Aembit | workload and agent access management across clouds |
| Adjacent | Keycard | identity and access for AI agents |
| Substitute approach | AWS Secrets Manager | storing agent credentials as secrets retrieved with IAM roles |
Recent news
- September 2026: Consent Portal added to AgentCore Identity. A hosted portal lets end users grant an agent consent to access resources on their behalf. [source]
- August 2026: AWS Agent Registry becomes generally available. Release notes list auto-detection with AWS Organizations and customer managed key encryption. It is a separate component from AgentCore Identity. [source]
- June 2026: Credential providers can reference AWS Secrets Manager secrets. Customers can keep secrets under their own Secrets Manager policies and reference them by ARN. [source]
- 30 April 2026: On-behalf-of token exchange generally available. Available in 14 AWS Regions. Exchanged tokens carry both user and agent identity. [source]
- April 2026: VPC egress support for Identity, Gateway and Runtime. Identity can connect to identity providers running inside customer VPCs. [source]
- March 2026: AgentCore Policy generally available. Release notes state availability in thirteen AWS Regions. [source]
- October 2025: Amazon Bedrock AgentCore generally available. Release notes state general availability across nine AWS Regions, following a preview in July 2025. [source]
What we could not verify
- Exact days of the July 2025 preview and October 2025 general availability: the release notes give months only.
- A Private Key JWT client authentication entry in the release notes carries a date that could not be reconciled with the other entries; it is not used here.
- Ping Identity integration guidance for AgentCore Identity is not confirmed in the sources reviewed.
- Whether AWS Agent Registry or AgentCore Policy provide ownership, discovery or review functions. Not reviewed in detail.
- CloudTrail coverage and log fields for AgentCore Identity operations were not reviewed.
This list covers points where public sources were missing, unclear or could not be opened. It is not complete. If you can supply a public source, tell us.
Additional sources for the sections above
- AWS What's New: Amazon Bedrock AgentCore Identity now supports On-Behalf-Of (OBO) token exchange (Official company announcement, 2026-04-30)
- AWS documentation: Features of AgentCore Identity (Official product documentation, 2026)
- AWS documentation: On-behalf-of token exchange (Official product documentation, 2026)
- AWS documentation: Amazon Bedrock AgentCore Identity (Official product documentation, 2026)
- AWS documentation: Amazon Bedrock AgentCore release notes (Official product documentation, 2026)
Other companies in this category
Amazon Bedrock AgentCore Identity is listed under Identity governance platforms with NHI coverage. The companies below share that category in our directory. This is a category listing, not a ranking, and inclusion does not mean the products are equivalent.
Scroll sideways to see all columns.
| Company | Ownership | Funding (as stated in its profile) | AI agent coverage (as stated) |
|---|---|---|---|
| Microsoft Entra Agent ID | Microsoft | Not in the profile summary | Yes (core; documented as generally available on a page last updated 1 May 2026) |
| Ping Identity | Private (owned by Thoma Bravo since October 2022) | Not in the profile summary | Yes (Identity for AI, generally available March 2026) |
| C1 (formerly ConductorOne) | Workday agreed to acquire C1 (definitive agreement announced 13 October 2026); completion not confirmed | More than $100M (company statement, October 2025) | Yes (agents as first-class identities with credentials, policies, lifecycle and ownership; AI Access Management, March 2026) |
| Lumos | Independent | Not publicly disclosed as a total. Announced rounds: over $30M (May 2022, reported) and $35M (May 2024) | Yes (governs agents; Identity Agent Force automates governance; MCP Governance checks agent tool calls, September 2026) |
| Oak | Independent | $60M seed | Yes (core) |
| Okta | Public (Nasdaq: OKTA) | Not in the profile summary | Yes (Okta for AI Agents; Agent SSO generally available August 2026; Cross App Access; Permiso detection) |
| SailPoint | Public (Nasdaq: SAIL); controlled by Thoma Bravo | Not in the profile summary | Yes (Agentic Fabric; Agent Identity Security; SailPoint Entro) |
| Saviynt | Private | Not stated by the company. Announced financings sum to about $1.075B: $170M total capital as of September 2021 (including a $130M financing), $205M in January 2023 and $700M in December 2025 | Yes (AI Agent Identity Management product) |
Frameworks and guides that apply to this category
- NHI access reviews
- ISO/IEC 27001 and machine identity
- SOC 2 and NHI
- NHI and IGA, PAM, CIEM
- Regulation and standards tracker
- NHI funding tracker
Related companies
Full list: NHI company directory.
Sources
- AWS documentation: Features of AgentCore Identity (Official product documentation, 2026)
- AWS documentation: Amazon Bedrock AgentCore Identity (Official product documentation, 2026)
- AWS What's New: Amazon Bedrock AgentCore Identity now supports On-Behalf-Of (OBO) token exchange (Official company announcement, 2026-04-30)
- AWS documentation: On-behalf-of token exchange (Official product documentation, 2026)
- AWS What's New: AWS Agent Registry now supports custom metadata for registry records (Official company announcement, 2026-10-13)
- AWS documentation: Amazon Bedrock AgentCore release notes (Official product documentation, 2026)
No company pays to appear on NHI Governance. Spot an error? Tell us; corrections are logged publicly.
About this record
Research summary. This profile is compiled from public sources by NHI Governance. Inclusion is not an endorsement, certification, security assessment or investment recommendation, and does not imply any partnership or affiliation with Amazon Bedrock AgentCore Identity. Names and trademarks belong to their owners. Statements marked as analysis are our opinion.
- Research status
- Researched from public sources; sources checked
- Last verified
- Next review due
- 2026-12-23
- Editorial responsibility
- Akshay Dubey (editor), HumanAudit Inc.
- Company input
- None recorded. Under our editorial policy, companies do not approve pages.
Something wrong or out of date? Report it. Companies have a right of reply.