Amazon Web Services has classified Nova Premier as Legacy with an end-of-life date of September 14, and Nova Canvas and two Nova Reel versions as Legacy with end-of-life dates of September 30, according to the company's Bedrock model-lifecycle schedule as of July 29. [1][3]
The dates convert a sourced report into an official schedule. A day earlier, the July 28 report that put Nova's retirement on the record before Amazon confirmed anything rested on unnamed sources and a strategy frame; this paper kept it below the line of Amazon confirmation, customer notice, migration terms, and replacement performance. The lifecycle page supplies the first of those missing stages. The rest remain open.
Legacy classification carries specific restrictions under AWS's published lifecycle rules: the models stop accepting new customers and new Provisioned Throughput commitments, and there is no automatic migration path to a successor. [3] Existing customers keep access until the end-of-life date. Nothing has shut down. A Legacy entry is a schedule, not an executed termination — but for a customer holding a Nova workload, the calendar is now a procurement document.
Nova 2 Omni has no announced cutoff, and the end-of-life frame does not extend to it. [1] What happens to that model — and whether the frontier team Amazon assembled under Pieter Abbeel ships a successor before September — is exactly the question the strategy reporting raises and the lifecycle page cannot answer. [1][2]
The two frames diverge on what the document is for. The press frame, led by MLQ's July 29 write-up, reads a strategy overhaul: Amazon winding down in-house foundation models to concentrate on its frontier effort. [1] The internal designation reported for the wind-down — "keep the lights on," or KTLO — and the overhaul framing itself remain report-sourced, not Amazon-confirmed. [1][2] The AWS-developer frame on X reads the same page as a forced-migration calendar with weeks, not quarters, on it: plan your Nova migration now, and check the 15-day-inactivity clause under which access to a model can lapse for a customer who stops calling it. Whether that clause applies to the Legacy models, and whether any customer has received formal notice beyond the schedule, is not established on the July 29 record. [3]
Custody matters here. The strongest dated write-up of the wind-down carries a July 30 dateline, after this edition's cutoff, and this account does not rely on it. The end-of-life claims above stand on the July 29 reporting and the lifecycle page's as-of-July-29 state. [1][3] A page that updates daily is evidence only of what it said when read.
What AWS owes its Nova customers between now and September is the unresolved commercial question: migration tooling, pricing on replacements, and notice breadth. [1] The strategy story tells a reader why Amazon moved. The schedule tells a reader with a production workload what the move costs and when. The second is the one with a deadline attached.
September 14 is six and a half weeks from Wednesday. That is not a strategy. It is a date.
-- DARA OSEI, London