The Change Applies Only to the Legacy Agent Service
This is not a shutdown of Amazon Bedrock, nor an immediate retirement of existing agents. AWS says Bedrock Agents Classic will continue to operate, and its existing APIs and infrastructure-as-code templates remain available, but it will not gain new features. Existing customers can continue using it; customers adopting AWS's agent platform for the first time after July 30 must start with AgentCore.
AgentCore Is the Official Migration Path
AWS recommends AgentCore's managed agent harness for most teams. Developers declare a model, tools, and instructions, while the platform handles the runtime, compute, memory, identity, and observability. Action Groups can be exposed as MCP tools through AgentCore Gateway. Teams that need a custom orchestration loop can still deploy code-defined agents using Strands, LangChain, the OpenAI Agents SDK, or the Claude Agent SDK.
What Development Teams Should Do
Existing workloads do not require an emergency migration, but further expansion on Classic will add future migration work. Teams should inventory their dependencies on Action Groups, Knowledge Bases, Guardrails, memory, and tracing, then use the AgentCore CLI to import and test current configurations. New projects that have not launched should adopt AgentCore directly to follow AWS's published product direction.
via: AWS Bedrock Agents Classic maintenance-mode guide, AWS service availability update; verified 2026-07-31