The date on the table was March
Business Insider reported on 28 July that Amazon is winding down most of its flagship Nova line, moving engineers and compute toward a Frontier Model Research group under Pieter Abbeel, with a new flagship model expected at re:Invent later this year. The reporting is accurate. It is also four months behind the only document that carries dates.
AWS publishes a model lifecycle table for Bedrock. It has listed Nova Premier and Nova Sonic as Legacy since 13 March 2026, and Nova Canvas and Nova Reel since 30 March, each with a hard end-of-life date attached: 14 September for the first pair, 30 September for the second. Nova Reel appears twice, at v1:0 and v1:1, both on the same schedule.
None of those rows were hidden. A model on Bedrock sits in one of three states, Active, Legacy or EOL, and the table publishes only the ones already sentenced. An engineer who opened that page in March saw the same dates a reporter described this week as a strategy overhaul.
What Legacy already took away
Legacy is not a warning about the future; it is a set of removals that have already happened. Once a model enters that state you cannot start new fine-tuning jobs against it, and you cannot create new Provisioned Throughput endpoints for it.
Existing commitments survive on narrow terms. Fine-tunes and Provisioned Throughput created before the model went Legacy keep working, and you can still create a new on-demand deployment of a custom model you had already trained. New customers are blocked outright.
The quietest clause deserves reading twice: existing customers may lose access to a Legacy model after 15 days of inactivity. A model you use seasonally, or one sitting behind a service that has been idle since spring, can become unavailable well before its end-of-life date.
So if you fine-tuned Nova Premier for a production workload, the freeze started on 13 March. Every retraining cycle you have planned since then was already impossible. The constraint had simply not been tested yet.
Two September dates, and no published reprieve
End-of-life falls on 14 September 2026 for Nova Premier and Nova Sonic, and 30 September for Nova Canvas and Nova Reel. AWS states that on or soon after the EOL date a model stops being available across all regions and requests to it fail. Migration does not happen automatically; you update your application code or it breaks.
There is normally a cushion. For models with EOL dates after 1 February 2026, a Legacy model enters a public extended access period after at least three months, during which active users can keep it until EOL at pricing the provider sets, which AWS warns will be higher. AWS says it notifies customers of that date when a model first enters Legacy.
The Nova rows carry no published extended access date. The rows beside them do: Claude Sonnet 4 shows July against an October end-of-life, and Claude Opus 4.1 shows October against January 2027. Same table, same column, and Amazon's own models are the ones without a stated fallback window.
Where the roadmap actually lives
Put the lifecycle page on a monthly calendar item, the way you already treat certificate expiry. On Bedrock the state is machine-readable as well: GetFoundationModel and ListFoundationModels return a modelLifecycle field, so the check can be a scheduled job rather than something a person has to remember to do.
European teams are inside this rather than watching it. Nova Canvas and Nova Reel are served from eu-west-1 in Ireland and Nova Sonic from eu-north-1 in Stockholm, so a workload pinned to an EU region for data residency carries the same two September dates with fewer places to fall back to. Nova Premier ran only in US regions, which is its own answer to whether it was ever a candidate for a residency-bound deployment.
The general rule outlasts Nova. A vendor's marketing tells you what it wants to sell you next; its deprecation table tells you what it has already decided to stop supporting, with dates attached. When the two disagree, the table is the one with a contractual consequence behind it.
Read next: When the Bill Says 7 Trillion, Do Not React | Your Human-Checked Data Was Already Part Machine



