AWS Agent Registry Old Namespace Shuts Down October 30: Migration Checklist for AI Agents

30 October 2026 | AWS's migration plan began 6 August 2026 | Status: announced shutdown deadline; live enforcement not independently tested. If your team registered AI agents, MCP servers or reusable agent skills using the public-preview AWS Agent Registry APIs, today's deadline deserves attention. AWS states that the old bedrock-agentcore registry namespace shuts down on 30 October 2026. Any registries and records left there lose read/write access. This is not a shutdown of Amazon Bedrock AgentCore Runtime, Gateway, Identity or Policy. It is a breaking migration for the Agent Registry component, documented in the official comprehensive migration guide.

What actually changes on October 30?

The new agent-registry namespace launched on 6 August. AWS allowed existing customers to use both namespaces during a migration window, which ends today. AWS explicitly says the migration is more than changing a URL: service endpoints, IAM actions, resource ARNs, SDK clients, CLI commands, event sources, record schemas and stored data must be addressed. This is a scheduled cutoff documented by AWS, not evidence that any particular customer's registry is already failing. See the migration timeline and before/after examples.

Why enterprise AI teams should care

Agent registries are the catalog through which developers discover approved agents, MCP tools and skills. A stale namespace can affect automated discovery, internal agent catalogs, CI/CD scripts, security policy evaluation and operational monitoring. The risk is specific to organizations that adopted the preview registry. A team using Bedrock AgentCore Gateway without AWS Agent Registry should not assume its gateway is being retired. First establish whether the old registry namespace is actually present in your estate.

The migration checklist

1. Find affected references. Search infrastructure-as-code, environment variables, application configuration, SDK initialization, API clients, CloudTrail queries and EventBridge rules for bedrock-agentcore-control, bedrock-agentcore registry endpoints and registry ARNs. Distinguish registry references from other AgentCore services that legitimately retain the old service prefix. The AWS namespace mapping explains this boundary.

2. Move endpoints and clients. Registry data-plane endpoints change from bedrock-agentcore.{region}.amazonaws.com to agent-registry.{region}.api.aws. Control-plane endpoints move to agent-registry-control.{region}.api.aws. Update the corresponding SDK client and CLI service namespaces. AWS's Agent Registry getting-started guide shows the new console and client approach.

3. Update access controls without broadening privileges. Registry IAM actions move to agent-registry:* and registry ARNs change. AWS says BedrockAgentCoreFullAccess does not automatically grant the new registry permissions. Use a least-privilege policy rather than blindly applying a full-access policy. Importantly, workload identity and OAuth credential provider operations remain under bedrock-agentcore; do not replace every occurrence. Verify the exact IAM action mappings and exceptions.

4. Migrate the data and update record schemas. AWS says existing registries and records must be extracted, transformed and loaded into the new namespace, in the same account and region. The new model adds required name and recordType fields; record descriptors and search filters also change. A namespace-only edit can therefore leave integration code incompatible. Review the supported record types and AWS's data migration and API schema guide before promoting changes.

5. Reconnect discovery and monitoring. The new discovery API is SearchDiscoverableRegistryRecords, replacing the old search operation. Test that approved agent and MCP records are returned as expected, including role-specific access. Update EventBridge event-source filters from aws.bedrock-agentcore to aws.agent-registry, along with CloudTrail and CloudWatch references. Consult the record search documentation and EventBridge event mappings.

How to verify migration is complete

Run a small controlled smoke test in the target AWS account and region: list the migrated registries; retrieve an approved record; perform a discovery search through the new API or MCP endpoint; verify expected access-denied behavior for an unauthorized principal; and confirm one registry event reaches the monitoring rule. Record the test timestamp, account/region, owner and outcome. Where migration is incomplete, escalate as a service-specific dependency rather than claiming a general AWS outage.

One detail that is easy to miss

The new registry is not simply a renamed catalog. Its API and data model changed. That means a developer may update endpoint configuration and still break an integration because the request schema, search operation or event filters remain old. For enterprise architects, the right migration evidence is a successful end-to-end discovery and authorization test, not a screenshot of a new console.

Bottom line

Deadline: 30 October 2026. Scope: AWS Agent Registry public-preview namespace only. AWS's documentation states the old namespace will shut down today, but this article does not independently confirm that the shutdown has already been enforced in every region. Inventory dependencies, migrate registry data and clients, adjust IAM and event rules, and validate the new discovery path. Start with the official AWS migration guide and the IAM reference. Teams with no old-namespace registry usage have no action from this specific deadline.