Amazon is winding down most of its flagship Nova models. Days after trimming jobs in its AGI group, the company has begun deprecating Nova Premier, Nova Omni, Nova Reel and Nova Canvas — the high-end, multimodal, video-generation and image-generation offerings that anchored the Bedrock catalog.
The reporting comes from Business Insider via Reuters. Amazon has not published a deprecation schedule or end-of-life dates, and a spokesperson pushed back with the standard line: "We're continuing to invest in and support the Nova models our customers rely on today." Fine. The practical takeaway is unchanged — if you have production traffic on these models, a forced migration is coming, and you should start it before Amazon hands you a deadline.
What's going away, what stays
| Deprecated | Still supported |
|---|---|
| Nova Premier (high-end flagship) | Nova 2 Lite |
| Nova Omni (multimodal) | Nova 2 Sonic |
| Nova Reel (video generation) | Nova Forge (build-your-own) |
| Nova Canvas (image generation) |
The pattern tells you where Amazon is headed. Resources are moving to a new frontier-model effort led by researcher Pieter Abbeel, with frontier research now a top priority, and the new flagship is expected to debut at re:Invent later this year — possibly still under the Nova brand, per Business Insider. The remaining chat offering, Nova 2 Sonic, does not slot in where Premier and Omni were being used. If your agents relied on Omni's multimodal input or Premier's reasoning depth, you do not have a like-for-like internal replacement today.
What this means for your Bedrock stack
The migration is mechanical on the surface: you swap the model ID in your request, or in your agent's tool configuration, and Bedrock routes to the new endpoint. The quality contract is not mechanical. Every prompt you tuned against Premier or Omni needs re-validation, and multimodal inputs need particular scrutiny since your replacement may not accept the same input mix.
This is the part I'd push on before touching code. Decide what you're migrating to first. Claude 3.x/4.x via Bedrock is the obvious candidate for text-heavy work, but if you want to stay inside Amazon's own catalog you are largely limited to Nova 2 Lite and Nova 2 Sonic today. That is a thin shelf. Most teams I know running on Amazon's in-house models would be better served treating the deprecation as the trigger to re-evaluate the model layer entirely, not to find a same-brand swap.
Either way, build the regression set before you switch. Your golden prompts, your eval outputs, the edge cases that made you pick Nova in the first place — all of that is the acceptance criteria, and you want it ready so the day you flip the model ID you can diff quickly rather than discover regressions in production.
Why this pattern keeps repeating
Amazon has struggled to generate buzz around Nova the way OpenAI, Anthropic and Google have, and has instead doubled down on selling the infrastructure. That strategic discomfort is now visible internally: AGI work was consolidated under cloud veteran Peter DeSantis in December, several top AGI executives have left over the past year, and the AGI group just had jobs trimmed. The Nova family itself has been reorganized repeatedly since its 2023 origins. When an org reshuffles this often, bets placed on its models carry real risk — today's deprecation is what that risk looks like when it lands.
The reminder, and it's one I keep coming back to: a foundational-model contract is only as durable as the vendor's willingness to keep funding it. Amazon's own spokesperson said it plainly — the lineup evolves "based on what customers need." That is not a guarantee; it is a warning that today's model is tomorrow's deprecation notice.
What I'd do this week
- Inventory. Grep your codebase and CloudWatch logs for every
amazon.nova-*model ID. Know exactly what depends on Premier, Omni, Reel or Canvas. - Lock down the golden set. Capture your highest-value prompts and their expected outputs before anything shifts under you.
- Pick a target. Decide between a same-brand fallback (Nova 2 Sonic/Lite) and a cross-vendor move via Bedrock, and get one spike running on it.
- Watch re:Invent. The new frontier model is expected there. If it ships under the Nova brand with different capabilities, that changes your migration calculus — but don't wait for it. Plan against what exists now.
Do the inventory and the golden set first. Those are cheap, and they make the eventual swap — whenever Amazon forces it — a controlled change instead of a fire drill.
Sources: