Sunday, April 12, 2026

The way forward for managing brokers at scale: AWS Agent Registry now in preview


Now accessible by means of Amazon Bedrock AgentCore, use AWS Agent Registry to find, share, and reuse brokers, instruments, and agent abilities throughout your group.

As enterprises scale to lots of or hundreds of brokers, platform groups face three essential challenges: visibility (realizing what brokers exist throughout the group), management (governing who can publish and what turns into discoverable organization-wide), and reuse (stopping groups from rebuilding capabilities that exist already). With out a centralized system, agent sprawl accelerates, compliance dangers develop, and improvement effort is wasted on duplicate work. These challenges are compounded by actuality: no group’s agent panorama lives fully inside one supplier. Brokers are constructed throughout AWS providers, different cloud platforms, and on-premises environments. A registry that solely covers a part of the stack leaves the remainder invisible, and invisible brokers can’t be found, ruled, or reused. Fixing this requires greater than a spot to listing what exists. Platform groups have to construct brokers, publish them with approval workflows, assist groups to find and reuse what exists, govern who can publish and devour, monitor what’s operating in manufacturing, and retire what’s not wanted. At present, we’re saying AWS Agent Registry (preview) in AgentCore, a single place to find, share, and reuse AI brokers, instruments, and agent abilities throughout your enterprise.

AgentCore is the platform to construct, join, and optimize brokers at scale, designed from the bottom up for brokers: open to any mannequin, any framework, any enterprise structure. Whether or not you’re delivery your first agent or your thousandth, you will have one platform that scales with you. The registry extends that very same flexibility to the way you arrange and govern what you’ve constructed. It indexes brokers no matter the place they’re constructed or hosted – on AWS, different cloud suppliers, or on premises.

What’s accessible in preview at this time

The registry shops metadata for each agent, device, MCP server, agent talent, and customized assets as a structured report. It captures who revealed every report, what protocols it implements, what it exposes, and find out how to invoke it. The registry helps established requirements like MCP and A2A natively, with the pliability to outline customized schemas to your group. There are two methods to register a report. You possibly can present metadata manually by means of the console, AWS SDK, or API, specifying functionality descriptions, possession, compliance standing, and utilization documentation. Or you possibly can level to an MCP or A2A endpoint, and the registry will mechanically pull within the particulars. Your registry can replicate your full agent panorama from day one, not solely the items that occur to run on AWS.

The registry is accessible by means of the AgentCore Console, APIs, and as an MCP server. Any MCP-compatible consumer can question it instantly, together with Kiro and Claude Code. For organizations with customized identification suppliers, OAuth-based entry signifies that groups can construct their very own discovery UIs with out requiring IAM credentials.

Discovering what already exists

With out a central registry, builders search externally for third-party instruments or duplicate work {that a} neighboring workforce already shipped. You lose visibility into what’s been constructed, who owns it, and whether or not it’s accepted to be used. The registry solves this with hybrid search that mixes key phrase and semantic matching: all queries use key phrase matching, however longer, pure language queries additionally use semantic understanding to floor conceptually associated outcomes. This implies a seek for “fee processing” surfaces instruments tagged as “billing” or “invoicing,” even when they’re named otherwise. Discovery turns into the trail of least resistance. Groups can search by title, descriptions, and useful resource sort to search out what already exists earlier than constructing one thing new. Builders search the registry first. If a vetted functionality exists, they use it. If it doesn’t, they construct it, register it, and make it accessible to everybody else. You possibly can see what exists throughout your group.

For Zuora, an AI-first monetization and income administration platform deploying 50 brokers throughout Gross sales, Finance, Product, and Developer groups, the AWS Agent Registry in AgentCore offers Principal Architects a unified view to find, handle, and catalog each agent, device, and talent in use. This centralized strategy allows groups to search out and reuse current property fairly than rebuilding from scratch. Standardized metadata ensures every agent and power consists of constant particulars on possession and capabilities, giving groups end-to-end visibility and accountability throughout the complete agent ecosystem.

– Pete Hirsch, Chief Product and Expertise Officer, Zuora

Governing what will get revealed

With out governance, anybody can register something. You lose management over what turns into discoverable, can’t implement requirements, can’t observe possession, and might’t handle brokers from improvement to retirement. When you will have just a few brokers, you possibly can handle them in a spreadsheet. When you will have lots of or hundreds, you want a system that enforces requirements mechanically.

The registry offers you management over what will get revealed and who can entry it. Admins use IAM insurance policies to outline who can register brokers, instruments, and agent abilities and who can uncover them. Each report follows an approval workflow: they begin as drafts, transfer to pending approval, and change into discoverable to the broader group as soon as accepted. The registry tracks brokers throughout their total lifecycle, from preliminary improvement by means of deployment to eventual retirement. Data are versioned to trace modifications over time, and organizations can deprecate information which might be not in use. The registry offers hooks to combine your current approval workflows. You possibly can add customized metadata to every entry by means of a report, capturing info like workforce possession, compliance standing, or deployment setting.

Southwest Airways is enabling an enterprise-wide agent catalog and governance throughout the enterprise. AWS Agent Registry in AgentCore solves the essential discoverability problem— enabling groups to search out and reuse current brokers as a substitute of rebuilding capabilities from scratch. With managed governance throughout a number of platforms, each agent carries standardized possession metadata and coverage enforcement. This can stop agent sprawl throughout the group whereas establishing the inspiration for scaling hundreds of brokers with enterprise-grade governance from day one.

– Justin Bundick, VP AI and Clever Platforms, Southwest Airways

The place we’re headed

We’re constructing towards a future the place the registry spans each AWS service the place brokers are constructed, together with Amazon Fast, and Kiro. Brokers shall be mechanically listed the second that they’re deployed. Builders will search from the IDE, enterprise customers will uncover brokers of their workspace, and admins will govern from the console, all backed by the identical supply of reality. Cross-registry federation will allow you to join a number of registries and search throughout them as one. It is possible for you to to outline classes and taxonomies that match how your group thinks about brokers, backed by structured metadata schemas capturing possession, compliance standing, value heart, and no matter else your governance mannequin requires. Over time, operational intelligence from AgentCore Observability will floor alongside registry information: invocation counts, latency, uptime, and utilization patterns, serving to you to grasp not solely what exists, however what’s actively working in manufacturing.

Past AWS Agent Registry, we’re constructing towards connecting with exterior companion catalogs. We’re enthusiastic about early companion curiosity in centralized discovery and governance throughout your know-how panorama.

Get began

At present’s preview is the beginning line. No extra rebuilding what already exists. No extra brokers deployed with out visibility. The AWS Agent Registry offers you one place to find, govern, and reuse each agent throughout your enterprise.

AWS Agent Registry is on the market in preview at this time by means of AgentCore in 5 AWS Areas: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Eire).

Get began with AWS Agent Registry by means of the AgentCore Console. Study extra by studying the documentation.


In regards to the authors

Preethi CN

Preethi CN is Director of AgentCore within the Agentic AI Group, with over 20 years of experience in embedded and cloud software program improvement. In her 14 years at Amazon, she has architected large-scale distributed programs and pushed AI improvements throughout Retail, Alexa, and AWS, delivering breakthroughs in multimodal AI. She led speech recognition for Alexa, Laptop Imaginative and prescient providers at AWS, and generative AI transformation that revolutionized how organizations extract insights from unstructured content material at scale. As a technical advisor to the Agentic AI Group, she has offered strategic oversight throughout Amazon Fast, Kiro, and AWS Rework. Most not too long ago, she crafted the imaginative and prescient and led the launch of AgentCore, the platform for constructing, connecting, and optimizing production-ready AI brokers at scale.

Related Articles

Latest Articles