Amazon Nova Premier reaches end of life on 14 September. Nova Canvas and two versions of Nova Reel follow on 30 September. If an application in production still calls one of those model IDs after the date, the calls fail. Bedrock does not quietly reroute traffic to a newer model, and AWS does not migrate applications on a customer's behalf.
That is twelve days for Premier. For teams that treated a hosted foundation model as infrastructure rather than a dependency, it is a short window.
The retirements are the visible end of a wider retreat. Business Insider reported in late July that Amazon is scaling back development across Nova Premier, Nova 2 Omni, Nova Canvas and Nova Reel — employees described them as running in “keep the lights on” mode — while resources move to a new frontier-model effort. AWS has separately classified Premier, Canvas and Reel as Legacy on its Bedrock lifecycle schedule. Nova 2 Omni sits in an odd middle: reportedly deprioritised, but with no published EOL date, so its status is not a confirmed shutdown.
What Legacy status actually restricts
Legacy is not a soft warning. Under Bedrock's lifecycle rules, new customers cannot access a Legacy model at all. Existing customers can keep calling it, but may lose access after 15 days of inactivity — which quietly punishes exactly the low-volume, seasonal or batch workloads least likely to be watching. No new Provisioned Throughput can be created, and fine-tuning against the underlying foundation model closes.
The published cadence is a model staying available for at least 12 months after launch, with at least six months in Legacy before EOL. That is a reasonable amount of notice. It is also notice that tends to arrive by email and console banner, land in an account nobody reads, and get discovered by an on-call engineer.
Migration is not a string swap
The failure mode people underestimate is the successful migration that breaks the application anyway. Swapping a model ID changes more than routing. Different models interpret system instructions differently, return different response structures, consume tokens at different rates, and carry different context limits, tool-use behaviour, content filtering, regional availability and price.
A contract-summarisation pipeline that depends on a specific JSON shape can move to a demonstrably better model and still fall over, because the parser downstream was written against the old output. The model works. The product does not.
Our take: This is the second time in two weeks that a model provider's roadmap has landed as an operational bill for its customers — and it will not be the last. The lesson is not “avoid Bedrock”; every hosted provider retires models, and AWS at least publishes a schedule. The lesson is that a model ID hard-coded in application logic is a dependency with an expiry date and no owner. Keep model IDs in configuration, keep an inventory of which workloads call which, and keep a frozen evaluation set you can re-run against a replacement in an afternoon. Teams that have those three things are looking at a sprint. Teams that don't are about to find out how many Lambda functions reference Premier.
What replaces what
Amazon says development continues on Nova 2 Lite, Nova 2 Sonic, Nova Forge and Nova Act. None is a drop-in substitute for every retiring workload: Forge is for customised model development, Act targets browser and interface automation. Bedrock's third-party catalogue is the other route, and for image and video generation in particular the alternatives are not obviously worse. They are, however, different, which is the whole problem.
Behind it sits a consolidation. Amazon put Pieter Abbeel in charge of a Frontier Model Research team in December 2025, when foundation-model development, custom silicon and quantum computing moved under senior vice president Peter DeSantis. Job cuts across the AGI organisation followed. Business Insider reported Amazon is targeting re:Invent 2026 for the frontier model's debut and may keep the Nova name; Amazon has not confirmed the timing or disclosed architecture, pricing or availability.
What to watch
- 14 September and 30 September. Hard dates. Test before them, not around them.
- The 15-day inactivity rule. The sharpest edge for infrequent workloads. Inventory batch and seasonal jobs first.
- Nova 2 Omni. No EOL date published. Reported deprioritisation is not a schedule, but it is not nothing either.
- re:Invent 2026. Unconfirmed. Finish migrations on the published dates rather than planning around an unannounced release.