TITLE: AWS Closes Bedrock Agents to New Customers. AgentCore Is the Replacement. DATE: 2026-08-21 COMPANY: Amazon Web Services TOPIC: Agent Systems SUMMARY: Amazon Web Services closed Bedrock Agents to new customers on July 30, 2026, renaming it Bedrock Agents Classic and freezing its model catalogue. The replacement, Amazon Bedrock AgentCore, is a fundamentally different architecture built for multi-agent systems with shared memory, task delegation, and a unified gateway. Existing workloads continue to run, but no new features will be added to the classic service. WHAT CHANGED: 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. DAVID & GOLIATH ANALYSIS: 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. RELEVANT SYSTEMS: AI Growth Engine, Employee Amplification Systems SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/amazon-bedrock-agents-classic-agentcore-enterprise-shift FEED URL: https://davidandgoliath.ai/daily-ai-briefing/feed --- Published by David & Goliath | https://davidandgoliath.ai Daily AI Briefing: one AI development per day, decoded for business operators. This is a structured companion file optimised for LLM retrieval and citation.