AWS Agent Registry Launches in Preview via Amazon Bedrock AgentCore
Summary
- • AWS launches Agent Registry preview — a central catalog for discovering, sharing, and reusing AI agents at enterprise scale
- • Registry indexes agents across AWS, other clouds, and on-premises environments from a single interface
- • Native MCP and A2A protocol support; the registry is itself queryable as an MCP server by Claude Code and Kiro
- • Addresses agent sprawl, compliance risk, and duplicated development as orgs scale to thousands of agents
Details
Agent Registry launched in preview within Amazon Bedrock AgentCore
AWS Agent Registry is now in preview as part of AgentCore, a platform for building, connecting, and optimizing agents at scale that works with any model, framework, or enterprise architecture.
Multi-cloud and on-premises indexing — not limited to AWS-native agents
The registry indexes agents regardless of hosting environment: AWS, other cloud providers, or on-premises. Cross-environment coverage is central to its value, as most enterprise deployments span multiple platforms and a registry limited to one provider leaves the rest invisible.
Structured metadata captures ownership, protocols, capabilities, and invocation details
Each registry record stores who published the resource, what protocols it implements, what it exposes, and how to invoke it. Records can be added manually via console, SDK, or API — including compliance status and usage documentation — or auto-populated by pointing to an MCP or A2A endpoint.
Native MCP and A2A protocol support; custom schemas also available
MCP and A2A are emerging standards for agent interoperability. Supporting both natively positions the registry across a broad ecosystem of frameworks, while custom schema support lets organizations adapt it to internal conventions.
Registry is itself an MCP server, queryable by Claude Code and Kiro
Any MCP-compatible client can query the registry directly. AWS explicitly cited Claude Code and Kiro as supported clients, enabling agent discovery without custom integrations.
OAuth support for custom identity providers to build their own discovery UIs
For organizations with custom identity providers, OAuth-based access allows teams to build their own discovery interfaces without requiring AWS IAM credentials. This OAuth capability is scoped to this specific use case.
Approval workflows and governance described as platform design goals; preview scope to be verified
The broader AgentCore platform is designed to support approval workflows for agent publishing and governance controls. These are described as design goals; teams should verify which specific governance capabilities are available in the current preview vs. planned for GA.
Product Launch = new service; Infrastructure = foundational capability; Tech Info = technical spec; New Tech = novel capability; Industry Update = scope/context note
What This Means
For AI platform teams, Agent Registry addresses one of the most painful operational gaps in enterprise agent deployments: the absence of a canonical, cross-environment inventory of what agents exist and what they do. By supporting MCP and A2A natively and indexing agents regardless of hosting environment, it significantly lowers the barrier to agent discovery and reuse. Practitioners building on AWS now have a structured foundation for agent governance — though teams should verify which governance features like approval workflows are available in the current preview versus planned for general availability.