AWS Agent Registry moves to a new namespace
AWS is moving Agent Registry to the agent-registry namespace and plans to end support for the public-preview bedrock-agentcore namespace on October 30.
AWS is moving Agent Registry to the agent-registry namespace and plans to end support for the public-preview bedrock-agentcore namespace on October 30.
Agent Registry ran in public preview under the bedrock-agentcore namespace.
AWS introduces the agent-registry namespace and lists October 30, 2026 as the end of support for the preview namespace.
AWS is documenting an ongoing migration for Agent Registry. The registry is available under the new agent-registry namespace, while support for the previous public-preview bedrock-agentcore namespace is scheduled to end on October 30, 2026.
Agent Registry is used to register and discover agents, MCP servers, skills and custom resources. For agent and MCP records, AWS validates descriptors against the relevant protocol schemas. The namespace change can therefore affect integrations, endpoints and automation that still point to the preview namespace.
AgentenCode records this as a lifecycle and infrastructure event for Amazon Bedrock AgentCore. It does not mean AgentCore itself is being discontinued; the documented transition concerns the public-preview namespace used by Agent Registry.
Teams should check API calls, IAM permissions, EventBridge events and other references for the old namespace. AgentenCode records the migration deadline as a verified fact but does not assume that individual AWS environments will be migrated automatically.
Primary source
What this update is based on
AgentenCode publishes product changes only after source-first review. The original provider source remains authoritative for current details.
Continue checking
Full context in the Agent Profile.
The profile, trust evidence and history separate documented properties from Unknown.