Bedrock Model Migration Sprint

Move every workload off a retiring Bedrock model before its end-of-life date (found across all your accounts, tested against your own traffic, rolled out in stages) and leave a lifecycle check behind so the next deadline isn't a surprise.

Overview

Bedrock models now retire on a published schedule. Claude Sonnet 4 reached end of life on October 14, 2026 and requests to it fail; Claude 3.x ends in more Regions on November 13, Opus 4.1 on January 8, a large batch of open-weight models on March 30 and Claude Sonnet 4.5 on April 8, 2027. Legacy models can cost more before they disappear, and can stop working for jobs that go fifteen days without running. We move you to current models without a regression, and leave you able to do the next one in an afternoon.

What we do

Find it

• Inventory every model ID and inference profile in use, from CloudWatch metrics, CloudTrail and invocation logs, across all accounts and Regions

• Include the places code search misses: Knowledge Bases, Agents, Flows, Step Functions and other teams' functions

Test it

• Build an evaluation set of 50–200 real requests with what good looks like

• Run current and candidate models side by side; score with code checks, an LLM judge and human review where it matters

Fix it

• Adjust prompts for instruction-following and formatting differences

• Update code for API changes — tool choice, structured outputs, reasoning effort, inference profiles and data-residency constraints

Ship it

• Roll out behind a flag or percentage, compare cost, latency and errors, then remove the old model from code, configuration and IAM

Make the next one routine

• Model IDs moved to configuration, a scheduled lifecycle check, and the evaluation set kept for next time

Deliverables

• Every workload on an Active model, with evaluation results for each

• The inventory, evaluation set and lifecycle check, in your repositories