SunsetDiff

Amazon Bedrock AI21 Jamba shutdown on November 26, 2026

The dataset has 2 Amazon Bedrock ids with shutdown date 2026-11-26: ai21.jamba-1-5-large-v1:0 and ai21.jamba-1-5-mini-v1:0. The legacy lifecycle page lists both as Legacy in us-east-1, with legacy date May 26, 2026, EOL date November 26, 2026, and public extended access start date August 26, 2026. It says: "The following models are in the Legacy state with an announced EOL date. Migrate to an Active model before the EOL date." It does not name a model ID. See /shutdowns/aws-bedrock-2026-11-26/ for the batch page.

Last reviewed . Publisher: SunsetDiff.

Steps

  1. Read the two ids and the Region. The table lists ai21.jamba-1-5-large-v1:0 and ai21.jamba-1-5-mini-v1:0. Both stored rows say us-east-1. Open each model page before you change a call. A Region that is not on the lifecycle row is not covered by this date.
  2. Find the ids in your code. Search the repository for both model ids. Also check SDK defaults, agent configs, and notebooks. The model cards' sample code still sends these ids with region_name us-east-1.
  3. Pick an Active model yourself. The lifecycle page says to migrate to an Active model, and to migrate to the latest model, before November 26, 2026. It does not name the id to send. This guide does not fill one in.
  4. Test the call you will keep. Call the id you chose from the Region you use, with a prompt you send now, before November 26, 2026. In us-east-1, call GetFoundationModel or ListFoundationModels and read modelLifecycle first.

Models shutting down

These rows are the Amazon Bedrock models in the dataset with shutdown date 2026-11-26. The model id links to its SunsetDiff model page. The Legacy date column is the deprecation_date stored on the row. The Regions column is region_or_platform_notes. The replacement column is the official replacement stored on the row. Not published means the field is empty.

The current lifecycle policy page says: "This page describes the model lifecycle policy for models launched on Amazon Bedrock on or after September 7, 2026. For models launched before this date, see Model lifecycle (Legacy)." Both model cards list launch date Aug 22, 2024, so the legacy page is the one that applies. That page says: "For Amazon Bedrock usage, only the dates on this page apply."

The legacy table says: "The following models are in the Legacy state with an announced EOL date. Migrate to an Active model before the EOL date." The recommended replacement on each row is Not published because the stored replacements list is empty. This guide does not fill one in.

2 Bedrock model ids with shutdown date 2026-11-26.
Model idLegacy date storedShutdown dateRegionsRecommended replacement
ai21.jamba-1-5-large-v1:02026-05-262026-11-26Regions listed on the lifecycle page: us-east-1 (legacy 2026-05-26).Not published
ai21.jamba-1-5-mini-v1:02026-05-262026-11-26Regions listed on the lifecycle page: us-east-1 (legacy 2026-05-26).Not published

Sources: Amazon Bedrock model lifecycle (legacy) , Amazon Bedrock model lifecycle , checked November 2, 2026.

Dates on the legacy table and the model cards

The legacy lifecycle table lists one row for each id. Both rows use the same dates. Public extended access start date is not a field on the dataset row. It is a column on that table.

Each model card lists "Model lifecycle: Legacy" and "Model EOL date: November 26, 2026". Each card also lists "EOL no sooner than: Aug 22, 2025". That older floor is not the announced EOL. The announced EOL on the card and on the legacy table is November 26, 2026.

Dates printed on the legacy lifecycle table for these two ids.
Model idRegionsLegacy dateEOL datePublic extended access start
ai21.jamba-1-5-large-v1:0us-east-1May 26, 20262026-11-26August 26, 2026
ai21.jamba-1-5-mini-v1:0us-east-1May 26, 20262026-11-26August 26, 2026

Sources: Amazon Bedrock model lifecycle (legacy) , Jamba 1.5 Large model card , Jamba 1.5 Mini model card , checked November 2, 2026.

Region, geo, and global ids

The lifecycle page says: "Model lifecycle state can differ by AWS Region. The Regions column in the following tables lists only the Regions covered by a model's announced EOL date." The Regions cell for both Jamba rows is us-east-1. To check the Region you call, use ListFoundationModels or GetFoundationModel and read modelLifecycle.

The regional availability page prints Legacy (EOL: 2026-11-26) in the In-Region column for us-east-1 on Jamba 1.5 Large and on Jamba 1.5 Mini. The Geo and Global cells on those two rows are empty.

Each model card's programmatic access table lists the Geo inference ID as Not supported and the Global inference ID as Not supported. This guide does not invent a us. or global. id for either model.

Each card's sample code still creates a bedrock-runtime client with region_name us-east-1 and sends that model's id. us-east-1 is the Region on the EOL row.

Sources: Amazon Bedrock model lifecycle (legacy) , Jamba 1.5 Large model card , Jamba 1.5 Mini model card , Regional availability by models , checked November 2, 2026.

Public extended access

The legacy page says: "During this public extended access period, active users of a Legacy model can continue to use it until the EOL date (for a minimum of 3 months), but you should expect higher pricing, which will be set by the model provider." The table lists August 26, 2026 as the public extended access start date for both ids. The page says pricing in that period is set by the model provider. It does not print a price. The model cards point at Amazon Bedrock pricing and do not print a token price either. This guide does not invent one.

While a model is Legacy, the same page says: "New customers can't use Legacy models and existing customers may lose access to Legacy models after 15 days of inactivity." And: "You can't create a new Provisioned Throughput for models in the Legacy state."

Source: Amazon Bedrock model lifecycle (legacy) , checked November 2, 2026.

What breaks

The legacy page says: "On, or soon after the EOL date, the model is no longer available for use in all AWS Regions and requests made to this version will fail, unless there is a private arrangement between you and the provider for continued access." It also says: "You will need to migrate to the latest model by updating your application code before the EOL date. Migration will not happen automatically." It does not print an exception name.

The Jamba 1.5 Large and Jamba 1.5 Mini model cards do not print an exception name or an error sentence for the EOL date. This guide does not invent one. The end-of-life sentence recorded for Claude 3 Haiku is a different model card. It is not quoted here.

Sources: Amazon Bedrock model lifecycle (legacy) , Jamba 1.5 Large model card , Jamba 1.5 Mini model card , checked November 2, 2026.

Shutdown batch page

/shutdowns/aws-bedrock-2026-11-26/ lists both Jamba ids. /shutdowns/aws-bedrock-2026-11-13/ is the Claude 3 batch. It is not this Jamba date.

A not-sooner-than date is a floor, not an exact shutdown day. Anthropic's deprecations table lists claude-opus-4-5-20251101 as Active, with Deprecated N/A and tentative retirement not sooner than November 24, 2026. The deprecation history on that page does not name a replacement. The date page is /shutdowns/anthropic-2026-11-24/. The walkthrough is Claude Opus 4.5 will not shut down before November 24, 2026.

Sources: Amazon Bedrock model lifecycle (legacy) , Anthropic model deprecations , checked November 2, 2026.

Find the model ids in your code

Search the repository for both ids. A hit is a candidate, not proof the call still runs. How to find every model ID in your codebase covers SDK argument names. The scan page builds a search from dataset ids that have a shutdown date.

The lifecycle page tells you to update application code before the EOL date. It does not name the id to send. Pick the Active model you will call, then send one real prompt before November 26, 2026. The pre-migration test checklist is the longer list: evals, rejected fields, token limits, tools, price, and latency. These rows do not store a price.

ripgrep

rg -n -w -e 'ai21.jamba-1-5-large-v1:0' -e 'ai21.jamba-1-5-mini-v1:0'

Source: Amazon Bedrock model lifecycle (legacy) , checked November 2, 2026.

Related SunsetDiff pages

All guides

Questions

Which Bedrock model ids reach end of life on November 26, 2026?

The dataset lists ai21.jamba-1-5-large-v1:0, ai21.jamba-1-5-mini-v1:0 with shutdown date 2026-11-26. The legacy lifecycle page lists both in us-east-1.

Does November 26, 2026 apply in every AWS Region?

The legacy page says: "Model lifecycle state can differ by AWS Region. The Regions column in the following tables lists only the Regions covered by a model's announced EOL date." The Regions cell for both Jamba rows is us-east-1. The regional availability page prints Legacy (EOL: 2026-11-26) for that Region. Each model card says the Geo inference ID and the Global inference ID are Not supported.

What is the official recommended replacement?

Not published. The recommended replacement is the official replacement stored on each row. ai21.jamba-1-5-large-v1:0: Not published. ai21.jamba-1-5-mini-v1:0: Not published. The legacy page says: "The following models are in the Legacy state with an announced EOL date. Migrate to an Active model before the EOL date." It also says: "You will need to migrate to the latest model by updating your application code before the EOL date. Migration will not happen automatically." Neither sentence names a model ID.

What error does Bedrock return after this end of life?

The legacy page says requests made to this version will fail. It does not print an exception name or an error sentence. The Jamba 1.5 model cards do not print one either. This page does not invent one.

Is there a /shutdowns/aws-bedrock-2026-11-26/ page?

Yes. /shutdowns/aws-bedrock-2026-11-26/ lists both Jamba ids: ai21.jamba-1-5-large-v1:0 and ai21.jamba-1-5-mini-v1:0.

What does public extended access mean here?

The legacy table lists August 26, 2026 as the public extended access start date. The page says: "During this public extended access period, active users of a Legacy model can continue to use it until the EOL date (for a minimum of 3 months), but you should expect higher pricing, which will be set by the model provider." It does not print a price for these two ids.

More guides

Deprecation alerts

We email you before models shut down. Unsubscribe anytime.

Deprecation alert signup
Providers (optional)