AWS previews Agent Registry
Amazon put an agent registry into public preview as part of Bedrock AgentCore to help enterprises track and govern many AI agents across teams and environments. The service is positioned to manage agent ownership, scope, tool permissions, state boundaries and lifecycle status rather than just create more workflows, signaling a control‑plane approach to agent sprawl. (infoq.com)
Amazon Web Services has put Agent Registry into public preview, adding a catalog for companies to track and govern growing fleets of artificial intelligence agents. (aws.amazon.com) The service sits inside Amazon Bedrock AgentCore, Amazon’s managed platform for running agents, and Amazon said the preview started on April 9, 2026. Agent Registry stores agents, tools, skills, Model Context Protocol servers, and custom resources in one private directory for an organization. (aws.amazon.com) An artificial intelligence agent is software that can call tools, use memory, and act across steps instead of answering one prompt at a time. Amazon said the registry adds semantic and keyword search, publishing workflows, and approvals so teams can find and reuse those agents instead of rebuilding them. (docs.aws.amazon.com) Amazon framed the problem as “agent sprawl,” with platform teams losing visibility into what agents exist, who owns them, and which ones are approved for wider use. Its machine learning blog said large organizations are already planning for “hundreds or thousands of agents,” which turns discovery and governance into an operations problem. (aws.amazon.com) The registry is built more like a control plane than a builder. Amazon’s documentation says teams can attach metadata, manage approval status, control discoverability, and let both people and agents search the catalog for approved resources. (docs.aws.amazon.com) That puts the product in the part of the market focused on managing agents after they exist, not just helping developers create new ones. InfoQ reported AWS is pitching ownership, scope, permissions, state boundaries, and lifecycle status as the core records enterprises need once agent projects spread across teams and environments. (infoq.com) Amazon also made the registry work with Model Context Protocol, or MCP, an emerging standard for connecting models to tools and data sources. AWS said organizations can publish MCP servers into the registry, which gives developers and agents one place to discover approved connectors. (docs.aws.amazon.com) Rivals are moving in the same direction from different starting points. Forbes wrote on April 10 that Amazon, Microsoft, and Google are all building governance layers for agent fleets, while CIO Dive said vendors are pushing centralized systems as enterprise adoption accelerates. (forbes.com) (ciodive.com) AWS has not presented Agent Registry as a finished general-availability service yet; the company calls it a preview feature inside Bedrock AgentCore. For customers already experimenting with large numbers of agents, the immediate pitch is simple: know what exists before the fleet gets too big to see. (aws.amazon.com)