AWS migrates healthcare AI agents to Bedrock AgentCore ahead of Classic cutoff

AWS migrated 20 agents from its open-source healthcare and life sciences catalog to Amazon Bedrock AgentCore. [1] These agents previously ran on Amazon Bedrock Agents Classic, a platform that will no longer accept new customers beginning July 30, 2026. [1] Prior to the migration, maintenance costs scaled with the number of agents because each agent required its own CloudFormation stack and Lambda function. [1]

Using Kiro CLI, an agentic development tool, the migration took approximately 2.5 hours of wall-clock time. [1] The process utilized a pattern-first approach alongside parallel AI subagents to condense what could have been a quarter-long project into brief working sessions. [1]

AWS is actively steering developers away from the Classic Bedrock Agents architecture ahead of its July 2026 cutoff for new customers. By publicizing a rapid, 2.5-hour migration using Kiro CLI, AWS aims to demonstrate that transitioning to AgentCore is not prohibitively time-consuming. Furthermore, the explicit mention of CloudFormation and Lambda bottlenecks suggests that AgentCore centralizes or streamlines underlying infrastructure compared to the older framework. What the sources don't address: Whether existing Bedrock Agents Classic customers will eventually face a forced migration or service deprecation date after the July 2026 cutoff for new users.