AWS Freezes Bedrock Agents, Calls It a Naming Update

AWS Locked New Customers Out of Bedrock Agents and Called It a Naming Update

New accounts now get an HTTP 403. The model catalogue is frozen. The FAQ on the same page says no action is required.

Amazon shipped Bedrock Agents in November 2023 as its answer to enterprise AI agents. As of Thursday it is called Bedrock Agents Classic, and AWS's own documentation describes it as something rather more final than the name change it claims to be.

What changed

Quoting the documentation: "Amazon Bedrock Agents (launched November 2023) is now Amazon Bedrock Agents Classic and will no longer be open to new customers starting on July 30, 2026." Accounts with no Bedrock Agents activity in the previous 12 months now receive AccessDeniedException (HTTP 403) on CreateAgent and InvokeInlineAgent. There is no exception process. And: "The model catalog available in Bedrock Agents Classic is frozen as of the maintenance mode effective date."

The FAQ that contradicts the page it is on

AWS's own FAQ states: "What about the name change to 'Bedrock Agents Classic'? This is a naming update only. No action is required on your part." That is not what the rest of the same document describes. New customers are hard-blocked with a 403, no new features are planned, and a platform whose model catalogue is frozen cannot adopt the models released after July 2026 — which, on current cadence, means it is functionally obsolete within two quarters. The reassuring detail that AWS has announced no end-of-life date is doing a great deal of work for a product that was just frozen. Aggregators are relaying this as a rename. It is a deprecation.

Two and a half years, start to freeze

The successor is AgentCore. Every enterprise that standardised on Bedrock Agents — on AWS's own recommendation — is now on a dead branch, with no migration deadline to plan against and no committed sunset date to escalate on. The absence of a deadline is not generosity; it is the absence of a commitment.

Why it is worth noticing

The agent platform layer is churning faster than the enterprises building on it can re-architect. This is a concrete, dated, vendor-documented instance of that churn, from the largest cloud provider, on an abstraction it introduced less than three years ago.

Why It Matters

Enterprises are being told to build durable agent infrastructure on platforms whose vendors are replacing the abstraction every two to three years — and the deprecation arrives labelled as a naming update.