AWS Agent Registry Moves to a New Namespace Starting August 6
AWS Agent Registry is moving from the bedrock-agentcore namespace to agent-registry, requiring preview users to update endpoints, IAM policies, SDK clients, scripts, and registry data.
AWS Agent Registry Moves to a New Namespace Starting August 6
On August 6, 2026, AWS Agent Registry began moving from the preview bedrock-agentcore namespace to agent-registry. The change may look small, but it matters for teams that built integrations against the public preview.
What needs to change?
AWS documentation says existing users should review endpoints, IAM policies, SDK clients, CLI scripts, and registry data. Missing one of these dependencies can lead to failed calls or incorrect permissions after the transition.
Agent Registry is designed as a centralized catalog for agents and tools with approval workflows, search, and MCP integration. The engineering lesson is that preview services can change names and interfaces before stabilization. A good architecture isolates service calls behind a small integration layer and keeps namespaces and endpoints in configuration rather than scattering them throughout a codebase.