Deprecating registry records
Migration Now Open
AWS Agent Registry has launched under the new agent-registry namespace. Support for the public preview bedrock-agentcore namespace will be discontinued on September 17, 2026. For migration instructions, see Comprehensive registry migration guide.
Overview
When you deprecate a registry record, you remove it from the discoverable data-plane APIs (SearchDiscoverableRegistryRecords, ListDiscoverableRegistryRecords, BatchGetDiscoverableRegistryRecord) and from the registry’s MCP endpoint. Deprecated is a terminal state — after a record reaches this state, you cannot edit it or transition it to any other state. You can still find the record by using the ListRegistryRecords and GetRegistryRecord APIs for auditing purposes, but you cannot un-deprecate it.
Deprecate a record for reasons like you have decommissioned the resource, a newer version of the resource is published (with an independent record in the registry), the resource has known issues due to which you do not want other builders to discover the resource, or internal policy requires removal of the resource record.
Deprecate a record
Console
-
Open the record detail page.
-
Choose the Update status dropdown, then choose Deprecate.
-
In the Update status dialog, enter a Reason for the deprecation.
-
Choose Update.
Note
Deprecation is available from any record status.