LLMSwaps

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

What Amazon Bedrock owes you before end-of-life

Amazon Bedrock counts its notice in months. A model entering the Legacy state carries a period of six months or 45 days, stated on the model card itself, after which it reaches end-of-life, is removed from every region, and requests to it fail. Migration will not happen automatically. As of 2026-09-22.

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 leavesopenHow long the warning lastsHow long the warning lasts — What Amazon Bedrock publishes: Six months or 45 days per modelHow long the warning lasts — What that leaves open: Which of the two applies is on the cardWhere the figure is publish…Where the figure is publishedWhere the figure is published — What Amazon Bedrock publishes: On the model card, before anything is scheduledWhere the figure is published — What that leaves open: So it is readable without a notice arrivingWhat happens at the endWhat happens at the end — What Amazon Bedrock publishes: Removed from all regions, and requests failWhat happens at the end — What that leaves open: No read-only or degraded mode is describedWho performs the moveWho performs the move — What Amazon Bedrock publishes: Migration will not happen automaticallyWho performs the move — What that leaves open: The successor is not chosen for you eitherCan access end soonerCan access end sooner — What Amazon Bedrock publishes: After 15 days of inactivity, once legacy beginsCan access end sooner — What that leaves open: Inactivity is not defined in calls or in volume
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the lifecycle page commits to between a warning and a removal. Recorded 2026-09-22.
What the page is askedWhat Amazon Bedrock publishesWhat that leaves open
How long the warning lastsSix months or 45 days per modelWhich of the two applies is on the card
Where the figure is publishedOn the model card, before anything is scheduledSo it is readable without a notice arriving
What happens at the endRemoved from all regions, and requests failNo read-only or degraded mode is described
Who performs the moveMigration will not happen automaticallyThe successor is not chosen for you either
Can access end soonerAfter 15 days of inactivity, once legacy beginsInactivity is not defined in calls or in volume

Inclusion rule. Filled from the platform's own model lifecycle page. A period stated for a non-video model is still counted here, because the policy is written for every model the platform serves. Order. The warning first, then what ends it, then what shortens it.

1Months, and a place to read them without being told

The longer figure in this register belongs here, and the more useful property is not its length but where it lives. The period sits on the model card, so a team can read it while choosing a model rather than discovering it in a notice.

That turns the question from how much warning will I get into how much warning does this particular model carry, which is answerable on the day of the decision and therefore actually gets asked.

2Two figures on one policy

Six months and forty-five days are a wide spread for a single commitment, and the page puts the choice on the individual model rather than on a rule. A reader cannot infer from the policy alone which one applies to anything.

So the policy is best read as a promise to state a figure rather than a promise about its size. Both readings are honest; only the second one survives a production asking what its actual runway is.

3The sentence that undoes the runway

Once the legacy period starts, an existing customer may lose access after fifteen days without activity. For anything but continuous use, that is the real deadline, and it is shorter than either published figure by an order of magnitude.

A serial production alternates between heavy generation and weeks of writing, which is exactly the pattern this clause catches. The register keeps that sentence in the ending early column as well, because it belongs to both.

A window in months, and a clause that shortens itThe legacy period is six months or 45 days depending on the model. Inside that window an existing customer may lose access after fifteen days of inactivity, so the effective runway for anybody between projects is a fortnight rather than a season.One legacy window, two ways out of itLegacy beginsDay 0The stateappears on themodel and inthe interface.Inactivitycut-offDay 15Access can endhere if themodel wentunused.End-of-life45 days or 6monthsRemoved fromevery region;requests fail.The earlier exit is the one nobody schedules around
Fig. 2 Both numbers come from the same page; only one of them survives the way a serial production actually uses a model.
  • 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
  • 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
  • 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
  • Whether the platform moves you across
    Migration will not happen automaticallyAmazon Bedrock, model lifecycle / recorded 2026-09-22
  • How access can end before the date
    Once the Legacy period begins, existing customers may lose access after 15 days of inactivityAmazon 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 Notice period. Same column, other entries: Gemini API, LTX Studio.