Manage agents, tools and skills at scale with AWS Agent Registry
AWS Agent Registry is now generally available: a single, searchable, governed catalog for the agents, tools, skills, and custom resources across your organization. This post explains what Registry is and walks through its publishing, curation, and discovery workflows, plus enterprise considerations and what's next.
Managing agents, tools, and skills at scale can be challenging for organizations. Teams often build in isolation without a shared record of what exists, who owns it, or whether it's been reviewed. This has shifted the focus from building agents and tools to discovering and governing them. AWS Agent Registry addresses these challenges by providing a single, searchable, governed catalog for agents, tools, skills, and custom resources within an organization's environment.
The Registry offers three key benefits for enterprises:
1. No authoritative inventory: Without a central registry, there's no single record of existing agents and tools, leading to duplicative effort, version drift, and scattered capabilities. AWS Agent Registry resolves this by offering a comprehensive and searchable catalog of all registered resources.
2. No cross-team discovery: When valuable tools, agents, and skills exist, they remain unused due to lack of discoverability. The Registry's Discovery Plane provides a curated view of only the resources that have passed the organization's approval bar, enabling developers and consumers to find the resources they need quickly and efficiently.
3. No governance or audit trail: Without a centralized registry, there's no way to track access, security reviews, and failure tracing. AWS Agent Registry ensures governance and audit trails by assigning owners, maintaining clear lineages, and providing trust signals about resources.
Registry supports four record types: Model Context Protocol (MCP) server, its tools, resources, and prompts; Agent2Agent (A2A) agent cards defining agents and their skills; agent skill definitions in markdown files and associated code/packages; and a custom descriptor that must be valid JSON.
The Registry operates through two complementary planes: the Governance Plane and the Discovery Plane. The Governance Plane is the authoritative store for resources within a defined scope, where admins configure rules for management, such as compliance and security signals, discovery policies, and custom metadata schemas. The Discovery Plane is what consumers interact with daily, presenting a curated, high-performance view of only the resources that have passed the organization's approval bar.
It supports semantic and lexical searches, providing summarized compliance and security indicators to aid decision-making without overwhelming the users with governance details.
Written by urgent.news from AWS Machine Learning's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
