TITLE: AWS Retires Bedrock Agents Classic: What Operators Must Do Now DATE: 2026-08-08 COMPANY: Amazon Web Services TOPIC: Agent Systems SUMMARY: Amazon closed Bedrock Agents Classic to new customers on July 30, 2026, freezing its model catalogue and beginning a formal migration push to Bedrock AgentCore. Existing agents continue to run, but they are locked to older models and will need to move to AgentCore to access future capabilities. Organisations that built production workflows on Bedrock Agents Classic now face a defined migration window before the service is fully wound down. WHAT CHANGED: Amazon launched Bedrock Agents in November 2023 as one of the first enterprise-grade managed agent platforms from a major cloud provider. It allowed organisations to build agents that could query knowledge bases, call APIs, and run multi-step reasoning workflows using foundation models available in Bedrock's catalogue. On July 30, 2026, Amazon rebranded the product to Bedrock Agents Classic and stopped accepting new customers. At the same time, it froze the model catalogue, meaning agents built on Classic can no longer be updated to use newer foundation models. Amazon Bedrock itself, including Knowledge Bases and Guardrails, is not affected. The freeze applies specifically to the agent runtime layer. The replacement is Bedrock AgentCore, which Amazon describes as a framework-agnostic runtime designed for production-grade agent workloads. AgentCore breaks what was a monolithic service in Classic into modular components: a runtime layer, a gateway for tool connections, persistent memory, identity management for agent-to-agent trust, and observability tooling. The Harness component, which handles agent orchestration, reached GA on June 17, 2026. Amazon has not announced a hard end-of-life date for Classic, but the pattern is clear: maintenance mode is the holding state before eventual sunset. How long that window lasts is unknown, and organisations that wait for a firm date are taking on unnecessary risk. WHY IT MATTERS: The capability gap is immediate and permanent. With the model catalogue frozen, Classic agents are locked to older models. Every new release from Anthropic, Meta, Amazon itself, or any other provider integrated into Bedrock will be available in AgentCore and not in Classic. That gap compounds with every passing month. Enterprise agent workloads are not easy to migrate at speed. Bedrock Agents Classic embedded its own opinionated approach to prompting, tool calling, and knowledge base retrieval. AgentCore uses a different architecture. Teams that built deeply on Classic will need to re-engineer workflows, not just swap a configuration flag. Third-party vendor exposure is underappreciated. Many software products integrated Bedrock Agents under the hood as their AI backbone. If you are using any AI-powered product running on AWS, there is a real chance it depends on Classic. Those vendors now carry migration debt, and they may not have communicated their timelines to customers. The model freeze creates compliance risk for some industries. Organisations in regulated sectors that must demonstrate they are using current, well-maintained AI systems may find that running on Classic conflicts with their AI governance obligations, particularly under the EU AI Act's newly enforced high-risk provisions. AgentCore's modular design is materially better for operators. The separation of runtime, memory, gateway, and identity into distinct services means teams can update individual components without redeploying entire agents. That architecture is more resilient for production workloads than Classic's bundled approach. This signals the speed of platform cycles in enterprise AI. A product launched in November 2023 entered maintenance mode by July 2026. Teams that treat AI infrastructure as a long-term stable platform are systematically underestimating replacement velocity. DAVID & GOLIATH ANALYSIS: The retirement of Bedrock Agents Classic in under three years is not a failure on Amazon's part. It is evidence of how fast the underlying technology has shifted. The architecture that looked sensible in late 2023 does not hold up well against the demands of 2026 production workloads. Modular, observable, memory-persistent agents are what enterprises actually need, and Classic was not built for that. What this means for operators is straightforward: stop treating your AI agent infrastructure as set-and-forget. The 10 to 200 person organisations we work with often build one automation, see it work, and move on. That approach creates quiet debt. The Classic situation is a reminder that active maintenance of your AI stack is now a baseline expectation, not an optional improvement. The positive read is that AgentCore is genuinely better. Multi-agent orchestration, proper memory management, and identity controls for agent-to-agent trust are the building blocks of the kind of compound automation that creates real competitive advantage. The migration is friction, but the destination is worth reaching. RELEVANT SYSTEMS: AI Growth Engine, Employee Amplification Systems SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/aws-bedrock-agents-classic-retired-agentcore-migration 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.