LLMSwaps

Which model each app runs today, and when it last changed

Three states, readable without opening a page

Three states are published here and the model itself carries the current one: Active, Legacy or End-of-Life. Because the value is readable through the interface, the moment to start a migration can be detected by software instead of by somebody remembering to check a documentation page. As of 2026-09-22.

What the lifecycle page publishes about the conditions a model passes through. Recorded 2026-09-22.
What the page is askedWhat Amazon Bedrock publishesWhat that leaves open
How many states are namedThree, from available to removedWhich is the largest number in this register
Where the current value livesOn the model, readable through the interfaceNot only in a table a human re-reads
What the middle state carriesA period of six months or 45 daysStated on the model card in advance
What the last state meansRemoved from every region, requests failWith no degraded or read-only mode

Inclusion rule. A state counts when the entry publishes the label itself. A marketing word such as new or classic is not a lifecycle state and does not fill a row. Order. How many states first, then what each one carries.

1A queryable state changes who has to remember

Every other entry in this column publishes a state on a page, which means somebody has to decide to look. Putting the value on the model turns the check into something a scheduled job does without being reminded.

That is the difference between a migration that starts when the state changes and one that starts when a person next happens to read the documentation. In a busy production the second one starts late.

A state on the model, not on a page somebody re-readsEvery other entry in this column publishes a condition on a documentation page, so somebody has to decide to look. Putting the current value on the model turns the check into something a scheduled job performs without being reminded.ActiveAvailable, and wherea new project shouldbe starting.Moves toLegacyNo new adoption. Aperiod of six monthsor 45 days begins.ThenEnd-of-LifeGone from everyregion. Requests toit fail outright.Three conditions, one of them queryableEverything difficult in this policy, including the inactivity clause, lives inside themiddle state.
Fig. 1 The difference between a migration that starts when the state changes and one that starts when a person next reads the docs.

2Three states describe a process rather than a switch

Available and gone are the two conditions any model has from outside. Naming a middle state with a period attached is what turns a removal into something with a beginning, and it is the part productions can actually plan inside.

It also tells a reader where to expect the interesting sentences. Everything difficult in this platform's policy, including the clause about inactivity, lives inside the middle state.

3The last state is uniform and blunt

After the final state the model is gone from every region and requests to it fail. There is no read-only period, no reduced service and no geographic remnant, which is unusually clear for a platform of this size.

Bluntness here is a feature. A state that half works is harder to plan around than one that stops, and the stored work reading records what that leaves behind.

  • The three states a model can be in
    Active, Legacy or End-of-Life, readable from the modelLifecycle fieldAmazon Bedrock, model lifecycle / recorded 2026-09-22
  • Legacy period
    Six months or 45 days, stated on each model cardwhich is the notice given before end-of-lifeAmazon Bedrock, model lifecycle / recorded 2026-09-22
  • What happens at end-of-life
    After the end-of-life date the model is removed from all AWS Regions and requests made to it failAmazon Bedrock, model lifecycle / recorded 2026-09-22

4Sources

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 Lifecycle states. Same column, other entries: Microsoft Foundry, Gemini API.