AWS Closes Bedrock Agents to New Customers. AgentCore Is the Replacement.

30-Second Summary

Amazon Web Services renamed Bedrock Agents to Bedrock Agents Classic on July 30, 2026 and stopped accepting new customers. The model catalogue is frozen at the maintenance mode date, meaning no new AI models released after that date will be available through the classic service. Existing customers can continue running their workloads, but the service will receive no new features. The replacement, Amazon Bedrock AgentCore, is a different architecture designed for multi-agent systems with shared memory, task delegation, and a unified gateway. For organisations building on AWS, the path forward is clear.

At a Glance

• Topic: Agent Systems, Enterprise AI Infrastructure
• Company: Amazon Web Services
• Date: July 30, 2026 (effective date of the change)
• Announcement: Bedrock Agents renamed to Bedrock Agents Classic and closed to new customers; AgentCore is the designated replacement
• What Changed: New customers can no longer access Bedrock Agents Classic. The model catalogue is frozen. AWS is directing all new agent development to AgentCore.
• Why It Matters: AWS is one of the dominant platforms for enterprise AI infrastructure. A platform deprecation at this scale signals a significant architectural shift in how agents will be built and run in enterprise environments.
• Who Should Care: Developers and technical leaders at companies building AI agents on AWS; any operator evaluating cloud infrastructure for AI workloads; strategic leaders tracking where major vendors are investing.

Key Facts

• Amazon Bedrock Agents Classic is no longer open to new customers as of July 30, 2026
• The service was launched in November 2023 and is now approximately 2.5 years old
• The model catalogue for Bedrock Agents Classic is frozen at the maintenance mode effective date
• New AI models released after July 30, 2026 are only available through AgentCore
• Existing allowlisted accounts retain full access to Bedrock Agents Classic with no announced end-of-life date
• AgentCore is positioned as a framework-agnostic runtime, meaning it is not tied to a specific agent SDK or orchestration library
• Microsoft shipped its unified Agent Framework 1.0 on April 3, 2026, merging Semantic Kernel and AutoGen into a single production SDK (Source: Microsoft)
• The Model Context Protocol, which governs how agents connect to business systems, shipped a major release candidate in August 2026 (Source: MCP Working Group)

What Happened

Amazon built Bedrock Agents in November 2023 as a managed service for creating single agents with basic tool-calling capabilities. For two and a half years, it served as the primary way AWS customers built AI agents in the cloud. On July 30, 2026, AWS renamed the service to Bedrock Agents Classic, closed it to new customers, and froze the model catalogue at that date.

The replacement service, Amazon Bedrock AgentCore, represents a different design philosophy. Where Bedrock Agents Classic was built around a single-agent model with basic tool calling, AgentCore is designed from the ground up for systems of agents. It includes dedicated services for runtime, gateway, memory, identity, and observability. These are treated as first-class infrastructure components rather than add-ons.

The gateway component is particularly significant. It provides a unified interface through which agents connect to external tools and data sources, governed by identity and access controls. The memory service allows agents within a system to share context across sessions and tasks. The observability layer is built in rather than retrofitted. Together, these components address the failure modes that made single-agent architectures brittle at scale: statelessness, poor access control, and the difficulty of debugging agent behaviour in production.

AWS did not announce a shutdown date for Bedrock Agents Classic. Existing workloads are protected by a maintenance mode commitment that guarantees continued access for allowlisted accounts. But the signal is direct: new investment and new models go to AgentCore.

Why It Matters

The single-agent era for cloud infrastructure is ending. Bedrock Agents Classic was a single-agent framework. AgentCore is infrastructure for agent systems. AWS is not the only vendor making this shift. Microsoft's Agent Framework 1.0 merged two previously separate products to create a unified multi-agent SDK. Google's Gemini Enterprise Agent Platform launched in August 2026 with an open partner ecosystem and multi-agent orchestration at its centre. The pattern is consistent: the major platforms are all moving from single-agent primitives to multi-agent infrastructure.

Model access is the forcing function for existing Classic customers. The frozen model catalogue is the detail that will drive migration timelines. AWS has a habit of releasing significant model improvements on short cycles. An organisation locked to the Classic model catalogue will find itself running progressively older models as new capabilities accumulate on the AgentCore side of the wall.

Framework-agnostic architecture is a significant change. Bedrock Agents Classic was opinionated about how you built agents. AgentCore is positioned as a runtime that works with whatever agent framework you prefer, including LangChain, CrewAI, AutoGen, or custom implementations. This lowers the switching cost for teams that have already invested in a particular framework and makes it easier to bring an existing architecture to AWS rather than rebuilding for the platform.

This is vendor consolidation, and consolidation reduces optionality. When a dominant cloud provider picks a winner in its own product portfolio, the market narrows. Teams that have built expertise in Bedrock Agents Classic will need to retrain. Documentation, community knowledge, and third-party tooling will shift toward AgentCore. Getting ahead of this transition is significantly cheaper than catching up after it has already happened.

Operators who are not AWS customers should still pay attention. Platform decisions by major cloud providers create norms that spread across the industry. The architectural patterns in AgentCore, shared memory, unified gateways, and built-in observability, are likely to appear in equivalent form in how Azure and GCP evolve their own agent platforms. Understanding where the infrastructure layer is heading helps operators make better decisions about which tools and frameworks to invest in, regardless of which cloud they run on.

The David and Goliath View

AWS shutting down access to a two-year-old service and redirecting everyone to a new architecture is not a shock. The surprise would be if this did not happen. The pace at which agent infrastructure is evolving means that any product built on 2023 design assumptions is already due for a rethink. What is worth noting is how consistently the major vendors are arriving at the same conclusions: single agents are not enough, memory is not optional, and observability needs to be built in from the start.

For operators who are not building their own agent infrastructure, this matters because the tools they use are built on top of these platforms. The agents embedded in CRMs, marketing tools, HR systems, and finance platforms are all running on infrastructure from AWS, Azure, GCP, or one of the emerging specialist providers. When that infrastructure shifts, the tools built on it shift too. You may not be making the architectural decisions yourself, but you are downstream of them regardless.

The practical question for most operators is simpler than it looks. If you are using AI tools built by someone else, track which cloud infrastructure your vendors run on and whether they are migrating. If you are building your own agents, even simple ones, treat the infrastructure choice as a five-year decision and pick accordingly. The cost of migrating agent infrastructure is not zero. It is measured in developer time, broken workflows, and downtime. Getting it right once is better than migrating twice.

Where This Fits in the AI Stack

This change sits at the infrastructure and runtime layer, one level below the agent frameworks developers use and two levels below the end-user applications that operators interact with. The stack from bottom to top: cloud infrastructure (AWS, Azure, GCP) provides compute, storage, and managed services. Agent runtimes (AgentCore, Azure AI Foundry) sit on top of that and provide the agent-specific services. Agent frameworks (LangChain, CrewAI, AutoGen, Microsoft Agent Framework) run on the runtimes and give developers a programming model. Applications built with those frameworks are what operators and their staff actually use. A change at the infrastructure layer propagates upward through all subsequent layers over time.

Questions Operators Are Asking

We are not on AWS. Does this affect us? Not directly, but it is a useful signal. AWS, Azure, and GCP all influence each other's roadmaps. The architectural decisions AWS is locking in with AgentCore, shared memory, unified gateways, and framework agnosticism, are likely to appear in how other providers evolve their platforms. Following this closely gives you early visibility into the direction of the entire infrastructure layer.

We are on Bedrock Agents Classic. Do we need to migrate now? No immediate action is required. Your workloads continue to run and AWS has not announced a shutdown date. The timeline pressure comes from the frozen model catalogue. Once you identify a model capability you need that is only available post-July 30, 2026, you will need AgentCore to access it. Start planning the migration now so it is a scheduled project rather than an emergency response.

What does AgentCore actually cost compared to Classic? AWS has not published a direct comparison at the time of writing. The cost structure for AgentCore reflects its expanded service set, including dedicated pricing for memory, gateway, and observability components. Expect the total cost of a production multi-agent system on AgentCore to be higher than an equivalent single-agent system on Classic, offset by the capabilities that come with the new architecture.

Is there an open-source alternative to avoid vendor lock-in? Yes. Agent frameworks such as LangGraph, CrewAI, and AutoGen can be self-hosted. The trade-off is that you take on the operational burden of running the infrastructure yourself. AgentCore's value proposition is that AWS manages that infrastructure for you. The right choice depends on your team's engineering capacity and your risk tolerance for vendor dependency.

How does this relate to the Model Context Protocol changes? AgentCore is designed to be compatible with MCP, which governs how agents connect to external tools and data sources. The major release candidate for MCP that shipped this month is being driven partly by enterprise teams using it to broker agent access to production systems. AgentCore's unified gateway is one of the key surfaces where MCP compatibility matters. Teams evaluating AgentCore should include MCP connector support in their assessment criteria.

Citable Summary

Amazon Web Services renamed Bedrock Agents to Bedrock Agents Classic on July 30, 2026 and closed the service to new customers, with the model catalogue frozen at that date. The replacement, Amazon Bedrock AgentCore, provides a framework-agnostic runtime for multi-agent systems, with dedicated services for memory, gateway, identity, and observability. Existing Classic workloads continue to run under a maintenance mode commitment with no announced end-of-life date. The change reflects a broader industry shift away from single-agent primitives toward infrastructure designed for multi-agent systems at enterprise scale. AWS, Microsoft, and Google have all made significant platform moves in this direction during 2026, signalling a convergence in how the major cloud providers are positioning agent infrastructure for enterprise use.