LLMSwaps

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

Removal from every region, and files left alone

The lifecycle page states that after the end-of-life date the model is removed from all regions and requests made to it fail. Material generated earlier is not addressed, because output on this platform is delivered to the caller's own storage rather than held in a product. 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 leavesopenIs disposal of material address…Is disposal of material addressedIs disposal of material addressed — What Amazon Bedrock publishes: Not addressed anywhere on the pageIs disposal of material addressed — What that leaves open: Output goes to storage the customer ownsWhat happens at end-of-lifeWhat happens at end-of-life — What Amazon Bedrock publishes: Removed from all regions, and requests failWhat happens at end-of-life — What that leaves open: Uniform, so no region is a hiding placeCan access end earlierCan access end earlier — What Amazon Bedrock publishes: After 15 days of inactivity in the legacy windowCan access end earlier — What that leaves open: Which is shorter than either published periodIs a fallback region describedIs a fallback region described — What Amazon Bedrock publishes: None, the removal is stated as globalIs a fallback region described — What that leaves open: So there is no geographic migration route
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the lifecycle page settles about the end of access. Recorded 2026-09-22.
What the page is askedWhat Amazon Bedrock publishesWhat that leaves open
Is disposal of material addressedNot addressed anywhere on the pageOutput goes to storage the customer owns
What happens at end-of-lifeRemoved from all regions, and requests failUniform, so no region is a hiding place
Can access end earlierAfter 15 days of inactivity in the legacy windowWhich is shorter than either published period
Is a fallback region describedNone, the removal is stated as globalSo there is no geographic migration route

Inclusion rule. Read from the model lifecycle page. Object storage or backup behaviour of other services on the same cloud is not read into this column. Order. The absence first, then how access ends.

1Global removal closes a door people expect to find open

Multi-region platforms train their customers to solve availability problems by moving. Stating that removal happens in every region removes that option explicitly, which is a clearer answer than most retirement pages give.

For a production it means the migration is to another model rather than to another place, and there is no interim arrangement to buy time with.

Removal is global, so migration is not geographicMulti-region platforms train customers to solve availability problems by moving. Stating that removal happens in every region closes that route explicitly, which leaves a migration to another model as the only path.The model reaches end-of-life. Where can the work continue?Another regionClosed offThe page states removalfrom all regions, notsome.Another modelThe only routeAnd no successor is namedfor you on the page.Files already madeUntouchedOutput went to storage thecustomer already owns.Which of the three the page actually addresses
Fig. 2 A clearer answer than most retirement pages give, and it removes an option people expect to find.

2Files are not the exposure here; capability is

Because delivery is to the customer's own storage, a retirement takes away the ability to make more and leaves everything already made. That is the good half of this arrangement and it is worth naming as an arrangement rather than as generosity.

The bad half is that a series needing more episodes in the same look has lost the means and kept the evidence. Which is precisely the case where knowing the model behind each file is what makes the problem sizeable at all.

3The inactivity clause reaches the same outcome faster

Access can end after fifteen days without use once the legacy window opens, so a production between blocks can lose the capability well before the published date and with no further notice.

The register keeps that sentence in ending early as well. It belongs to both columns because it changes the runway and it changes the moment regeneration stops being possible.

  • 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

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 Stored work. Same column, other entries: Gemini API, Wan-AI.