LLMSwaps

Announced end dates for video models, and which apps still carry them

A platform that says it will not move you

Amazon Bedrock is explicit about the part other pages leave implied: migration will not happen automatically. The lifecycle page describes states, a period and an end, and does not name a successor for any model. The customer chooses the destination and performs the move. From 1 source page, read 2026-09-22; no maker pays to be listed.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhat Amazon Bedrock publishesWhat AmazonBedrock publishesWhat that leaves openWhat that leavesopenIs a successor namedIs a successor named — What Amazon Bedrock publishes: No replacement is named for any modelIs a successor named — What that leaves open: The page is about states, not about choicesWho performs the moveWho performs the move — What Amazon Bedrock publishes: Migration will not happen automaticallyWho performs the move — What that leaves open: Stated plainly rather than left to be assumedWhat happens if nobody movesWhat happens if nobody moves — What Amazon Bedrock publishes: Requests fail once end-of-life passesWhat happens if nobody moves — What that leaves open: Removal is from every region, not stagedIs there help identifying affected workIs there help identifying affected work — What Amazon Bedrock publishes: Not described on the lifecycle pageIs there help identifying affected work — What that leaves open: The state is readable, the exposure is not
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the lifecycle page settles about who moves and where to. Recorded 2026-09-22.
What the page is askedWhat Amazon Bedrock publishesWhat that leaves open
Is a successor namedNo replacement is named for any modelThe page is about states, not about choices
Who performs the moveMigration will not happen automaticallyStated plainly rather than left to be assumed
What happens if nobody movesRequests fail once end-of-life passesRemoval is from every region, not staged
Is there help identifying affected workNot described on the lifecycle pageThe state is readable, the exposure is not

Inclusion rule. Read from the platform's model lifecycle page. A migration tool documented elsewhere in the service does not fill a cell in this column. Order. The absence first, then the sentence that makes it explicit.

1Saying it is better than implying it

Most pages in this column simply have nothing about succession, which leaves a reader free to imagine that a platform of this size handles it. This one closes that door in a single sentence, and the sentence is the most useful line in the column.

It converts an assumption into a task. A team that has read it knows the migration is on their plan, and can size it while a model is still active rather than during a legacy window.

2No destination, but a state you can query

The page names no successor, so the choice is genuinely open. What it does provide is a lifecycle state on the model itself, which means the trigger for starting the work can be automated even though the work cannot.

That pairing is unusual. Elsewhere in this register the trigger is a human remembering to re-read a page, and a migration nobody is reminded to start is a migration that begins after the deadline.

An automated trigger and a manual moveThe lifecycle state sits on the model and can be read by software, so the moment to start a migration is detectable without anybody remembering to check a page. The migration itself is stated to be the customer's work.The stateActive, Legacy or End-of-Life,on the model itselfReadable by softwareA trigger that fireswithout anyone watchingThe periodSix months or 45 days, on themodel cardPublished in advanceA runway you can sizebefore choosingThe moveNot performed for you, and nosuccessor namedStays with youWork to schedule, not newsto wait forOne retirement, three things the page settlesWhat the customer is left holding
Fig. 2 Elsewhere in the register the trigger is a human re-reading a page, which is how a migration starts after the deadline.

3What a resale layer does to the sentence

This platform resells models other companies make. So the sentence about not migrating you sits on top of another company's retirement decision, and the customer is downstream of both.

The register keeps that chain explicit by recording the platform's policy here and each maker's dates on the calendar. Neither layer is complete alone, and no page published by either of them joins the two.

4Production that outlasts a model

Model end dates touch “Amazon Bedrock”; SceneMixer's guides describe how its pipeline treats the models it runs:

Each scene gets an automatic AI 3D model, and every shot in the scene is generated against it.

SceneMixer, Why a Whole Series Stays Consistent on SceneMixer — “Does the layout of a room really stay the same across shots?” (read 2026-10-13)

A script is read once per project; switching affects new tasks, such as regenerating a storyboard.

SceneMixer, Which text tier for reading and storyboards — “Do I need to re-read the script when I switch?” (read 2026-10-13)

5Sources

Read from the model lifecycle page on docs.aws.amazon.com, 2026-09-22. The whole entry is on Amazon Bedrock, and the column it sits in is on Named replacement. Same column, other entries: LTX Studio, Kling AI.