AWS closed its original Bedrock Agents to new customers on July 30. It told nobody but the docs.
No blog post, no keynote, no press release. A maintenance-mode page in the Bedrock user guide is the only public record that Amazon retired the product it launched in November 2023, and it tells existing customers they will never get another new model inside it.
Amazon Web Services has stopped taking new customers for Amazon Bedrock Agents, the managed agent-building product it launched in November 2023, and it did so without saying so anywhere except a documentation page. The page, titled "Amazon Bedrock Agents Classic maintenance mode," states that the product "is now Amazon Bedrock Agents Classic and will no longer be open to new customers starting on July 30, 2026." We could find no AWS blog post, What's New entry or executive statement announcing the change. The docs page was live and unchanged as of Monday.
The details in that page are more consequential than the rename. Any AWS account without Bedrock Agents activity in the previous 12 months now gets an HTTP 403 when it calls CreateAgent or InvokeInlineAgent. AWS reproduces the error text: "Bedrock Agents is in Maintenance Mode. New agent creation is not available for accounts without prior service usage." The allowlist is automatic and per account. A company that runs a dozen AWS accounts and built agents in three of them keeps those three and loses the other nine. Asked, in its own FAQ, whether a customer can request an exception, AWS answers in two words: "No. There is no exception process."
The catalog is frozen for good
The part that should worry existing customers is the model freeze. "The model catalog available in Bedrock Agents Classic is frozen as of the maintenance mode effective date (July 30, 2026)," the page says. "New models released after that date will be available through AgentCore." Bedrock itself keeps getting new models. The orchestration layer that customers wrapped around those models does not. An enterprise that built a customer-service agent on Bedrock Agents in 2024 can run it indefinitely, but on whatever models existed in July, forever, unless it rebuilds.
AWS frames the situation gently. There is "no migration deadline" and "no planned end-of-life date." Pricing does not change, because Bedrock Agents never carried its own charge. But the same FAQ concedes that "no new features will be added to Bedrock Agents Classic," and every recommendation on the page points at a different product. That product is Amazon Bedrock AgentCore, which AWS now describes as "the platform to build, connect, and optimize AI agents."
Migrate by asking an agent to do it
The recommended migration path is itself a small sign of the times. AWS points customers to the agent toolkit for AWS on GitHub, which ships an "amazon-bedrock" skill for coding agents. The instructions are literal: install the toolkit, enable the skill, then "Prompt your agent with 'Help me migrate my Bedrock Agent to AgentCore harness.'" The skill inspects the old agent, checks eligibility, maps each component to its AgentCore equivalent and drives the AgentCore CLI to scaffold and deploy the replacement. AWS says it "never modifies your source agent" and pauses for approval before deploying.
The mapping table AWS publishes is candid about what does not carry over. Stage-specific prompt overrides, one of the features that made Bedrock Agents attractive to teams tuning pre-processing and post-processing behavior, "are not directly replicated." Multi-agent collaboration is listed as "Limited," with routing-mode multi-agent "not straightforward today." Custom orchestrators survive only if you deploy your own code on the AgentCore runtime. For straightforward agents AWS estimates the work in hours. For anything with a custom orchestrator or supervisor pattern it promises "more significant code work," which is the phrase every platform team has learned to read as a quarter.
Why the silence matters
Product sunsets happen. What is unusual here is the mismatch between the weight of the change and the volume at which it was communicated. Bedrock Agents was AWS's flagship answer to the agent wave for two and a half years. It was the managed AWS primitive that the company's own guidance pointed agent builders toward. Closing it to new accounts and freezing its models is the kind of decision that normally arrives with a deprecation blog post and a customer email. Instead it arrived as a new page in the user guide, and the only coverage we can find is from independent bloggers and newsletters who stumbled on the 403.
That matters for anyone choosing an orchestration layer now, because the lesson generalizes. The agent stack is consolidating fast. Microsoft folded two agent frameworks into one this summer, and AWS has now done the equivalent by moving every new customer to AgentCore. The frameworks and managed loops of 2023 and 2024 are becoming the "Classic" tier of 2026, and the switching cost lands on the customers who adopted earliest. It also sharpens a security point we made when attackers hijacked an AI gateway with a path to Bedrock: a frozen orchestration layer is one that will never receive a new safety-tuned model either.
AWS has not published a reason for the quiet rollout or a formal end-of-life date, and we will update this story if it does. In the meantime the practical advice is on AWS's own page. If your agents live in an account that has been quiet for a year, check whether you are still on the allowlist before you assume you can create anything. And if you are picking a home for agents that need to run for a long time, it is worth asking each vendor the question AWS just answered by omission: what happens to the models when you move on to the next product?
