Bedrock Agents Classic Is in Maintenance: Now What?
Amazon Bedrock Agents Classic entered maintenance on July 30, 2026. Here's exactly what changed, who's affected, and how to plan your move to AgentCore.
The Original Bedrock Agents Just Got an Eviction Notice — Read the Fine Print Before You Panic
On July 30, 2026, Amazon Bedrock Agents — the agent framework AWS shipped back in November 2023 — officially became Amazon Bedrock Agents Classic and entered maintenance mode. The headlines writing themselves ("AWS retires its flagship AI agent product") are a little dramatic. But the change is real, it has a date attached, and if you've built on the Classic
CreateAgent / InvokeInlineAgent APIs, you need to understand exactly what did and didn't just happen.Here's the calm, builder-level read.
What actually changed
Three concrete things took effect on July 30, 2026:
- No new customers. Accounts that had no Agents Classic activity in the preceding 12 months lose access to
CreateAgentandInvokeInlineAgent. If your account was dormant, the door is now closed.
- The model catalog froze. The set of foundation models available inside Agents Classic is locked as of the effective date. No new models will be added to Classic — so the shiny releases landing in Bedrock (Claude Sonnet 5, GPT-5.6, and the rest of the 2026 refresh) won't show up there.
- Maintenance mode. The service keeps running but gets no new features. It's in preservation, not development.
What did NOT change (breathe)
This is the part the scary headlines bury:
- Existing workloads are unaffected. If your account has recent Agents Classic activity, your agents keep running and you can still create and invoke them.
- Your other Bedrock investments are untouched. Foundation models, Knowledge Bases, and Guardrails are all separate services and continue exactly as before. Nothing about RAG pipelines or safety layers you built on Bedrock is deprecated here.
- Your IaC still works. Existing CloudFormation / Terraform templates that create or manage Bedrock Agents continue to function for allowlisted (active) accounts.
So this is not a "your production agent stops working on Monday" event. It's a "this product line has stopped evolving, and the newer path is where investment is going" event.
Where AWS wants you to go
AWS's recommended successor is Amazon Bedrock AgentCore — the newer, modular agent platform that treats the agent runtime, memory, identity, observability, and tools as managed primitives rather than a single monolithic "agent" object. Practically, AgentCore is where the 2026 momentum lives: the managed harness for going from declaration to working agent quickly, Guardrails wired in to screen every agent action, a Web Search tool, batch evaluation and A/B testing of agent versions, and continuous-learning features announced at the New York Summit.
The architectural mental-model shift is worth naming: Classic asked you to configure an agent. AgentCore asks you to compose capabilities — and makes the session itself a first-class cloud resource you can observe and govern.
What I'd actually do
If you're running on Agents Classic today, resist both panic and complacency. My playbook:
- Confirm your account is "active." Check whether you've invoked Agents Classic in the last 12 months. If yes, you retain access; if not, you're already locked out of creating new ones and migration just became urgent.
- Inventory the coupling. List every place your app calls
CreateAgent/InvokeInlineAgent/InvokeAgent, and note which Knowledge Bases and Guardrails they lean on. The good news: those dependencies port over — it's the orchestration layer, not the data layer, you're rebuilding.
- Pin your risk to the model freeze, not an outage. The real deadline pressure isn't a shutdown; it's that Classic will never get the newer models. If your roadmap needs Sonnet 5 or GPT-5.6 behind an agent, that's your true forcing function.
- Prototype one agent on AgentCore before you commit. Rebuild your simplest production agent on the managed harness, measure the latency and cost delta, and let that inform the migration estimate for the rest.
- Don't rush low-value agents. Maintenance mode means existing agents keep running. A stable internal tool that doesn't need new models can wait behind your higher-value migrations.
The honest tradeoff: AgentCore is more powerful and more composable, but "compose capabilities" carries more surface area than "configure an agent." Budget for a learning curve, not just a code port.
The bigger signal
Zoom out and this is AWS drawing a clear line: the monolithic 2023-era agent object is the past, and a managed, observable, governable agent stack is the future. Classic entering maintenance barely two and a half years after launch is a reminder of how fast this layer of the stack is churning — and why coupling your business logic tightly to any one agent framework is a risk worth designing against.
If you've started your Classic-to-AgentCore migration, what surprised you most — the parts that ported cleanly, or the parts you had to rethink from scratch? I'd love to compare notes.
#AWS #Bedrock #AgentCore #GenAI #AIAgents #MachineLearning
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article