# Amazon — Govern and discover records with common metadata in AWS Agent Registry

- Company: Amazon (amazon.com)
- Announced: 2026-11-17T20:31:04+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://aws.amazon.com/blogs/machine-learning/govern-and-discover-records-with-common-metadata-in-aws-agent-registry/
- Record: https://forck.live/items/37546-govern-and-discover-records-with-common-metadata-in-aws-agent-registry
- Subject: Bedrock / Nova

AWS added custom metadata schemas to AWS Agent Registry, letting administrators define organization-wide key-value fields that every registered agent, MCP server and skill must carry. Until now, organizations had no way to define these facts in the registry and store them on each record, so attributes such as business units, owners and risk classifications could not be tracked consistently. An administrator defines field names, types, allowed values and whether each field is required, and the registry validates every record against that schema. Records created without custom metadata are saved as NON_COMPLIANT and cannot be submitted for approval until required fields are filled, while unknown fields, missing required fields or invalid values are rejected with a ValidationException. GetRegistryRecord returns a record's metadata values and compliance status, and COMPLIANT means the values match the schema rather than that the record is approved. Metadata values are indexed for search, so consumers and agents can combine natural-language queries with filters such as environment=prod AND businessUnit=payments AND securityScanStatus=PASSED, and only approved records are returned.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/govern-and-discover-records-with-common-metadata-in-aws-agent-registry/:

> As organizations build more agents, Model Context Protocol (MCP) servers and skills, they need a consistent way to describe, govern, and find them. AWS Agent Registry provides a catalog for registering, approving, and discovering these resources and custom records. Each record carries a name, a description, a protocol descriptor, and an approval status. However, every organization has attributes and facts that it wants to track, and some are unique to that organization, such as its business units, resource owners, risk classifications, and development environments. Organizations want one common definition for each of these attributes, and they want every agent, MCP server, and skill in the registry to carry these facts. Until now, organizations had no way to define these facts in AWS Agent Registry and store them on each record.
> 
> Custom metadata schemas are now available in AWS Agent Registry. A custom metadata schema is a set of organization-defined key-value pairs that records in an AWS Agent Registry carry. An administrator defines the schema and applies it to the registry, and all records within the registry must then adhere to the schema.

---

Record: https://forck.live/items/37546-govern-and-discover-records-with-common-metadata-in-aws-agent-registry
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
