# AWS Agent Registry adds schema-validated custom metadata > Teams can define shared and resource-specific metadata fields, validate entries and filter registry searches through AWS interfaces. Canonical URL: https://www.devobs.io/news/news-event-525034fb62fdf43125582acb/ By: Lucas Vale Published: 2026-10-14T14:29:45.624Z Updated: 2026-10-14T14:29:45.624Z Event date: 2026-10-13 Section: AI AWS announced custom metadata support for AWS Agent Registry on October 13, 2026. According to AWS, the feature lets organizations attach structured fields to registry records for agents, MCP servers, agent skills, gateways and custom resources. [AWS announcement](https://aws.amazon.com/about-aws/whats-new/2026/10/aws-agent-registry-custom-metadata-registry-records) ## Shared attributes, resource-specific fields Teams define a schema once per registry, combining common attributes with fields specific to resource types. AWS gives team ownership, data classification and review status as examples, along with a model-family field for agent records. Supported field types are free text, URLs, Booleans and choices from a list of allowed values. AWS says the registry validates required fields and values whenever a record is created or updated. Search results can then be filtered on any custom metadata field through the AWS Management Console, AWS CLI, AWS SDKs or the registry’s MCP endpoint. [Schema and search details](https://aws.amazon.com/about-aws/whats-new/2026/10/aws-agent-registry-custom-metadata-registry-records) ## Structured labels are not a completed review For engineering teams, the practical opportunity is a shared vocabulary. A review-status field with allowed values can reduce inconsistent labels in free-form descriptions, while type-specific fields accommodate differences between resource categories. The operational question is who maintains those values. A required ownership entry should not, by itself, be treated as proof that the named team still owns the resource. Teams adopting the feature should assign responsibility for metadata updates and distinguish a recorded review status from the underlying review process. ## Availability: five AWS Regions AWS says custom metadata is available in every Region where Agent Registry is offered: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo) and Europe (Ireland). [Regional availability](https://aws.amazon.com/about-aws/whats-new/2026/10/aws-agent-registry-custom-metadata-registry-records) ## Source references -