AWS Fires the First Shot in the Agent Registry War, and Your LLM Collective Has Groupthink

We covered the enterprise agent visibility crisis on April 9: half of all organizations cannot see their own agents. Here is what happened since.

AWS responded with a product. Amazon Bedrock AgentCore now includes Agent Registry, a managed catalog that lets organizations register, discover, and govern AI agents regardless of where they run. The registry supports both MCP and A2A protocol descriptors, making it cloud-agnostic by design. Agents start as drafts, move through an approval workflow, and become discoverable only after vetting. The registry itself is accessible as an MCP server, so other agents can programmatically query it to find tools and capabilities. Hybrid semantic search means developers can find an "invoicing agent" by searching for "billing tools." (AWS Blog · InfoWorld)

Forbes framed the launch as the opening move in a platform war: whoever owns the registry layer controls discovery, and discovery determines which agents get used. The governance features (IAM-based access, lifecycle tracking, deprecation workflows) position this as infrastructure for operations teams, not just builders. For enterprises struggling with agent sprawl, a centralized registry with approval gates is the minimum viable governance layer. (Forbes)

Governance signal: If your organization deploys agents across multiple clouds or frameworks, a registry is no longer optional. AWS just made it a managed service. Expect Google Cloud and Azure to follow within months.

Investment signal: The agent middleware market is now a cloud-provider competition. Startups building standalone agent registries face a "build vs. buy" headwind from day one.