Which models Amazon Bedrock carries

Amazon Bedrock (docs.aws.amazon.com) publishes a three-state lifecycle for every model it resells, commits to either six months or 45 days of notice depending on the model, and states that migration will not happen automatically. As of 2026-09-12.

Inclusion rule. States and periods named on the platform's own lifecycle page. Individual model dates live on each model card and are not copied here, because the card is where they are added. Order. In the order the page presents the states.

1How many models each application names

Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.

Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.

2An end-of-life no sooner than date is a new kind of cell for this register

Most of this register records a date or a blank. This platform publishes a third thing: a floor. Each model card carries a date before which the model will not reach end-of-life, plus the length of the notice period that will precede it. A production can therefore plan against a guarantee rather than against an announcement, which nothing else tracked here offers.

It is worth being precise about what the floor is not. It is not a promise that the model stays available until then and no longer; it is a promise that the ending cannot arrive earlier. Combined with a stated notice period, that gives a team the two numbers it actually needs: the soonest possible bad news, and how long it gets once the bad news arrives.

3Two clauses that can end access before the date does

Once a model enters its legacy period, new customers cannot adopt it and existing customers may lose access after fifteen days of inactivity. For a series that shoots in bursts, that is the sharper risk than the end-of-life date: a production which pauses for three weeks between episodes could return to a model it is no longer entitled to call, without any date having passed.

The page also states plainly that migration will not happen automatically, which is the opposite of the arrangement at Microsoft Foundry, where some deployment types are upgraded for you and preview ones are moved whether you want it or not. Neither behaviour is better in the abstract. Being moved silently and being stranded silently are both continuity problems, and the useful thing is that both platforms say which one they do.

4Read column by column

This register reads Amazon Bedrock along notice period, named replacement, stored work, default tier, lifecycle states and ending early. One page each.

• Notice period — a legacy window of six months or 45 days, stated on the model card in advance
• Named replacement — states outright that migration will not happen automatically, and names no destination
• Stored work — the model leaves every region and requests fail; material is the customer's own problem
• Default tier — a request names a model identifier, so the default lives in the customer's own code
• Lifecycle states — three states, published on the model and readable through the interface
• Ending early — fifteen days of inactivity can end access inside a window measured in months

5Sources

Menu taken from the model lifecycle page on docs.aws.amazon.com, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

• 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
• 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
• Whether the platform moves you across
  Migration will not happen automaticallyAmazon Bedrock, model lifecycle / recorded 2026-09-22