Superpower Daily
AWS’s Bedrock Chat Blueprint Carries Tenant Filters Across Ever...DeepSeek Releases 305B Vision Weights Under MIT License, but Lo...Broadcom Releases AgentMinder to Check AI Agent Tool Calls at R...Microsoft Releases GigaPath-Flash, Reporting Roughly 50x Less C...Claims Adjusters’ AI Backlash Hits 98% Negative Reviews as Insu...Deloitte Buys Wavicle Assets to Add Databricks Engineering to I...AWS’s Bedrock Chat Blueprint Carries Tenant Filters Across Ever...DeepSeek Releases 305B Vision Weights Under MIT License, but Lo...Broadcom Releases AgentMinder to Check AI Agent Tool Calls at R...Microsoft Releases GigaPath-Flash, Reporting Roughly 50x Less C...Claims Adjusters’ AI Backlash Hits 98% Negative Reviews as Insu...Deloitte Buys Wavicle Assets to Add Databricks Engineering to I...
Productspublished

AWS Agent Registry Reaches GA With Approval Gates for Enterprise Agent Discovery

The service makes approval status a condition of discovery, separating a complete administrative record from the capabilities available for enterprise reuse.

By 3 min read
AWS Agent Registry Reaches GA With Approval Gates for Enterprise Agent Discovery
AWS Agent Registry Reaches GA With Approval Gates for Enterprise Agent Discovery
Sign in to save and react

Listen to this story

The audio brief

About 1:38
0:001:38
Read transcript
AWS has made AWS Agent Registry generally available, with a notable rule: an agent, tool, or skill is not discoverable until an administrator or curator approves it. That creates two separate layers. The Governance Plane keeps the complete administrative record, including drafts, rejected entries, ownership, versions, lifecycle status, audit trails, and metadata such as cost center, data classification, and service-level tier. The Discovery Plane is the smaller, consumer-facing catalog. Developers, business users, and autonomous agents can search it by exact name or by semantic intent, but shadow records and unapproved resources stay hidden. The registry supports four formats: Model Context Protocol servers, Agent2Agent agent cards, Markdown-based skills with associated code or packages, and valid JSON custom descriptors. The underlying problem is decentralized development. When teams build agents in isolation, an organization can lose track of who owns a capability, whether it is maintained, or whether an existing tool should be reused instead of rebuilt. AWS says the registry is designed to address that with access controls, approval workflows, and lifecycle tracking. AWS cites companies including Sony, Southwest Airlines, PepsiCo, and Amdocs as adopters or evaluators. Informatica is working on hosted MCP integration, while Check Point is adding discovery and security-posture assessment for Amazon Bedrock AgentCore workloads. The constraint is that some richer governance signals remain forward-looking, so the initial release is chiefly about cataloging, approval, and controlled discovery.

Story brief

3 key points

AWS Agent Registry is now generally available as a controlled catalog for agents, MCP servers, A2A agent cards, skills, and custom descriptors. Its key operational choice is to separate the full administrative record from the smaller set resources users and autonomous agents can discover after approval. That gives enterprises ownership, versioning, metadata, lifecycle, and audit mechanisms without exposing drafts or...

  1. 01

    The registry supports four record types: MCP servers, A2A agent cards, Markdown-based skills, and valid JSON descriptors.

  2. 02

    Consumers search only administrator- or curator-approved resources; drafts, rejected entries, and shadow records remain undiscoverable.

  3. 03

    Governance metadata can include cost center, data classification, and service-level tier, though some richer signals are forward-looking.

AWS has made AWS Agent Registry generally available, giving organizations a searchable catalog for AI agents, tools, skills and custom resources. Its defining mechanism separates the records administrators govern from the approved resources that people and autonomous agents can discover.

AWS is targeting a management problem that follows decentralized agent development. The company says isolated team collections can leave organizations without a shared record of ownership, maintenance or review, while teams that cannot find an existing capability may rebuild it. Registry is designed to add access controls, lifecycle tracking, approval workflows, ownership, versioning and audit trails to registered resources.

A catalog with two different audiences

The Governance Plane holds comprehensive resource records, including resources at different lifecycle stages. Administrators can configure discovery policies, compliance and security metadata, and custom metadata schemas. AWS gives cost center, data classification and service-level tier as examples of fields an organization can standardize there.

The Discovery Plane is the consumer-facing layer. Only resources approved by an administrator or curator appear there; draft, rejected and shadow records do not. Consumers can search the approved catalog by exact name or semantic intent, such as seeking a capability by the task it performs.

AWS diagram showing Agent Registry governance and discovery access surfaces.
AWS depicts separate governance and discovery access surfaces for Agent Registry. Source: aws.amazon.com.

The catalog covers more than agent cards

The registry supports four distinct record types: Model Context Protocol, or MCP, servers; Agent2Agent, or A2A, agent cards; skills described in Markdown with associated code or packages; and valid JSON custom descriptors.

  • Administrators set up registries, guardrails and governance processes.
  • Publishers register agents, tools and skills for broader discovery.
  • Curators approve or reject resources, while consumers can be developers, business users or autonomous agents.

Partners are building on the registry

AWS cites Sony, Mitsubishi Electric, Southwest Airlines, PepsiCo, Syngenta and Amdocs as customers or early adopters using or evaluating the registry. Informatica is building an integration for its hosted MCP servers to be listed, discovered and securely integrated through AWS Agent Registry. Check Point is integrating Registry for discovery and security-posture assessment of Amazon Bedrock AgentCore workloads.

The product’s current scope comes with a stated horizon: AWS says some of the richer Governance Plane capabilities it describes, including additional governance signals, are forward-looking. That leaves the initial release centered on cataloging, approval and discovery rather than the fuller governance view AWS says it plans to surface over time.

Sources

  1. aws.amazon.comManage agents, tools and skills at scale with AWS Agent Registry | Amazon Web Services

Related coverage

Continue reading