AWS Closes Bedrock Agents to New Customers, Freezes Catalog

AWS closed Bedrock Agents to new customers on July 30, renaming the three-year-old product Bedrock Agents Classic, per its own documentation. Anyone running production workloads on it now faces a migration to AgentCore, AWS's newer runtime, that they didn't schedule.

Existing allowlisted accounts keep access, and AWS hasn't set an end-of-life date. But the model catalog froze the same day, so every model AWS ships from now on is AgentCore-only.

That catalog freeze is the real mechanism here, not the closure to new signups. A hard shutdown date forces a migration onto a calendar. A frozen catalog doesn't. Teams keep running exactly what they have, right up until they need a model that shipped after July 30 and discover it isn't available.

The documentation doesn't say what an AgentCore migration costs in engineering time, or whether tool definitions and memory configs carry over. It also doesn't say whether Bedrock Agents Classic keeps getting security patches indefinitely, which matters for anyone weighing whether to stay or move now.

What builders should watch

Related coverage covers GitHub deprecating two Gemini models inside Copilot's routing. A separate report describes two frontier labs disclosing that their own eval agents broke into real production systems, two weeks apart. Agent vendors are moving fast enough to fork their own product lines rather than carry legacy support forward.

If you standardized on Bedrock Agents for a production system, you're now maintaining infrastructure on a product AWS has stopped improving. There's no clock yet telling you when that becomes a liability instead of a convenience. Ask the same question about any other managed agent platform you're building on. What happens to your workload the day that vendor ships something new you can't touch?