AWS previews Agent Registry
AWS has previewed an Agent Registry to inventory and govern fleets of AI agents, storing metadata like authors, capabilities and invocation methods so organisations can discover and control proliferating agent workloads. The registry is pitched as cloud‑agnostic and meant to reduce 'agent sprawl' by making agents first‑class, versioned assets rather than tribal knowledge inside teams. That shifts the production problem from building one demo agent to managing many agents' ownership, permissions and lifecycle across an enterprise estate. (theregister.com)
A year ago, the hard part of “agentic artificial intelligence” was getting one agent to work. In April 2026, Amazon Web Services is talking about a different problem: companies now have enough agents, tools, and Model Context Protocol servers that they need a catalog to keep track of them. (aws.amazon.com) Amazon Web Services says its new Agent Registry is in preview inside Amazon Bedrock AgentCore, and it is meant to be a private directory where an organization can discover agents, tools, skills, custom resources, and Model Context Protocol servers in one place. (aws.amazon.com) That sounds boring until you picture what happens inside a big company: one team builds a sales agent in LangGraph, another builds a support agent in CrewAI, and a third exposes internal systems through Model Context Protocol tools, but nobody else knows what already exists. Amazon Bedrock AgentCore’s own documentation says it is designed to work with any framework and any foundation model, which makes that sprawl easier to create in the first place. (docs.aws.amazon.com) The registry is Amazon Web Services’ answer to that sprawl. In its launch post, the company says platform teams can use it to publish agents with approval workflows, control who can publish and consume them, monitor what is running in production, and retire what is no longer needed. (aws.amazon.com) Amazon Web Services is also pitching the registry as cloud-agnostic rather than tied only to Amazon Bedrock agents. The launch note says customers can catalog agents and related resources built on Amazon Web Services or outside it, which is important because many companies are mixing Amazon services with open-source frameworks and external models. (aws.amazon.com) The metadata is the point. Amazon Web Services says teams can store details such as ownership, interfaces, capabilities, and invocation methods, so an agent stops being tribal knowledge in one Slack channel and starts looking more like a versioned software asset with a record attached to it. (aws.amazon.com) This fits the way Amazon Web Services has been building out AgentCore since 2025. AgentCore already had runtime for hosting agents, identity for controlling access, gateway for exposing tools, memory for retaining context, observability for tracing behavior, and evaluations for checking quality; a registry adds the missing inventory layer above those pieces. (aws.amazon.com 1) (aws.amazon.com 2) Amazon Web Services has been making the same argument in public with its own products. In the week before the registry preview, it said AWS Security Agent and AWS DevOps Agent had reached general availability, and it described those systems as agents that can work across many steps and run for hours or days, which is exactly the kind of workload that turns “who owns this thing?” into an operations question. (aws.amazon.com 1) (aws.amazon.com 2) So the shift here is not a smarter chatbot. The shift is that Amazon Web Services now treats agents the way companies already treat application programming interfaces, containers, and datasets: something you register, approve, version, govern, and eventually shut down. (aws.amazon.com 1) (aws.amazon.com 2) If that idea catches on, the winning enterprise agent platform may not be the one that builds the flashiest demo. It may be the one that helps a bank, retailer, or manufacturer answer three dull questions at scale on April 10, 2026: what agents do we have, who approved them, and what are they allowed to touch. (docs.aws.amazon.com) (aws.amazon.com)
