SunsetDiff

Amazon Bedrock open-weight models shutdown on March 30, 2027

The dataset has 30 Amazon Bedrock ids with shutdown date 2027-03-30. The legacy lifecycle page lists each one as Legacy, with legacy date September 30, 2026, EOL date March 30, 2027, and public extended access start date To be announced. The page does not use the words open-weight. 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. It also 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."

Last reviewed . Publisher: SunsetDiff.

Steps

  1. Read the ids and the Regions. The table lists every Bedrock id in the dataset whose shutdown date is 2027-03-30. The Regions column is the note stored from the lifecycle page. A Region that is not on that row is not covered by this date. Open the model page before you change a call.
  2. Find bare ids and prefixed ids. Search the repository for the bare model ids and for the geo ids in the cross-Region table. Also check SDK defaults, agent configs, and notebooks. A us. or us-gov. prefix is a different string from the bare id.
  3. Change modelId yourself. The lifecycle page says to update application code before March 30, 2027. It does not name the id to send. On the Converse API, that string is the modelId argument. A same-family Active id later in this guide is not an AWS recommendation.
  4. Test the call you will keep. Call the id you chose from the Region you use, with a prompt you send now, before March 30, 2027. Call GetFoundationModel or ListFoundationModels in that Region and read modelLifecycle first.

Models shutting down

These rows are every Amazon Bedrock model in the dataset with shutdown date 2027-03-30. 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 last column is the official replacement stored on the row. no official replacement means that list 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)." These rows are on the legacy page. That page says: "For Amazon Bedrock usage, only the dates on this page apply." It also 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 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." Every stored replacements list on these rows is empty. AWS did not name a replacement. This guide does not write one into the dataset.

The lifecycle page names one DeepSeek-V3.1 row with two ids: deepseek.v3-v1:0 on bedrock-runtime and deepseek.v3.1 on bedrock-mantle. It does the same for Kimi K2 Thinking (moonshot.kimi-k2-thinking on bedrock-runtime, moonshotai.kimi-k2-thinking on bedrock-mantle) and for both Qwen3 Coder rows. The page names the 27B Google model Gemma 3 27B PT and prints the model ID google.gemma-3-27b-it. There is no separate DeepSeek V3 id on that table.

30 Bedrock model ids with shutdown date 2027-03-30. AWS did not name a replacement.
Model idLegacy date storedShutdown dateRegionsOfficial replacement
deepseek.r1-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
deepseek.v3-v1:02026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-north-1, eu-west-2, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-runtime.no official replacement
deepseek.v3.12026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-north-1, eu-west-2, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-mantle.no official replacement
google.gemma-3-12b-it2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
google.gemma-3-27b-it2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
google.gemma-3-4b-it2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama3-1-70b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama3-1-8b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama3-3-70b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama3-70b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: ap-south-1, ca-central-1, eu-west-2, us-east-1, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama3-8b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: ap-south-1, ca-central-1, eu-west-2, us-east-1, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama4-maverick-17b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-1, us-west-2 (legacy 2026-09-30).no official replacement
meta.llama4-scout-17b-instruct-v1:02026-09-302027-03-30Regions listed on the lifecycle page: us-east-1, us-east-2, us-west-1, us-west-2 (legacy 2026-09-30).no official replacement
minimax.minimax-m22026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
minimax.minimax-m2.12026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-central-1, eu-north-1, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
mistral.devstral-2-123b2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-central-1, eu-north-1, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
mistral.mistral-7b-instruct-v0:22026-09-302027-03-30Regions listed on the lifecycle page: ap-south-1, ap-southeast-2, ca-central-1, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-west-2 (legacy 2026-09-30).no official replacement
mistral.mixtral-8x7b-instruct-v0:12026-09-302027-03-30Regions listed on the lifecycle page: ap-south-1, ap-southeast-2, ca-central-1, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-west-2 (legacy 2026-09-30).no official replacement
mistral.voxtral-mini-3b-25072026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
mistral.voxtral-small-24b-25072026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
moonshot.kimi-k2-thinking2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-runtime.no official replacement
moonshotai.kimi-k2-thinking2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-mantle.no official replacement
nvidia.nemotron-nano-12b-v22026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
nvidia.nemotron-nano-9b-v22026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
qwen.qwen3-coder-30b-a3b-instruct2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-central-1, eu-north-1, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-mantle.no official replacement
qwen.qwen3-coder-30b-a3b-v1:02026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-central-1, eu-north-1, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-runtime.no official replacement
qwen.qwen3-coder-480b-a35b-instruct2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-north-1, eu-west-2, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-mantle.no official replacement
qwen.qwen3-coder-480b-a35b-v1:02026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-north-1, eu-west-2, us-east-2, us-west-2 (legacy 2026-09-30). Platform listed on the lifecycle page: bedrock-runtime.no official replacement
zai.glm-4.72026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-north-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement
zai.glm-4.7-flash2026-09-302027-03-30Regions listed on the lifecycle page: ap-northeast-1, ap-south-1, ap-southeast-2, ap-southeast-3, eu-central-1, eu-north-1, eu-south-1, eu-west-1, eu-west-2, sa-east-1, us-east-1, us-east-2, us-west-2 (legacy 2026-09-30).no official replacement

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

What a call does after this date

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 model cards checked for this date do not print one either. This guide does not copy the Claude 3 Haiku exception onto these ids.

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."

The public extended access column on every one of these rows says To be announced. 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 ids. This guide does not invent one.

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

Cross-Region inference profile ids

The dataset stores the bare model ids. A geo id adds a prefix. The cards below print a geo inference ID. None of them print an eu. prefix. Global inference ID is Not supported on each of these rows.

The DeepSeek-R1 card's Converse sample sends modelId us.deepseek.r1-v1:0 with region_name us-east-1. Changing only deepseek.r1-v1:0 leaves that prefixed id in place.

Llama 3 70B Instruct and Llama 3 8B Instruct print Not supported for the geo inference ID and for the global inference ID. The other model cards in this shutdown set also print Not supported for both. That includes DeepSeek-V3.1, Gemma 3, MiniMax M2, MiniMax M2.1, Devstral 2, Mistral 7B, Mixtral 8x7B, both Voxtral ids, Kimi K2 Thinking, both Qwen3 Coder ids, GLM 4.7, and GLM 4.7 Flash. The Nemotron mantle rows also say Not supported. This guide does not invent an eu. id for any of them.

The limited model selection page says: "When a model reaches its End-of-Life date, it's no longer available through the inference profile. A replacement model might not be offered through the same inference profile for you to migrate to."

Geo inference IDs printed on the model cards for this shutdown date.
Model idEndpointGeo inference IDGlobal inference ID
deepseek.r1-v1:0bedrock-runtimeus.deepseek.r1-v1:0Not supported
meta.llama3-1-70b-instruct-v1:0bedrock-runtimeus.meta.llama3-1-70b-instruct-v1:0Not supported
meta.llama3-1-8b-instruct-v1:0bedrock-runtimeus.meta.llama3-1-8b-instruct-v1:0Not supported
meta.llama3-3-70b-instruct-v1:0bedrock-runtimeus.meta.llama3-3-70b-instruct-v1:0Not supported
meta.llama4-maverick-17b-instruct-v1:0bedrock-runtimeus.meta.llama4-maverick-17b-instruct-v1:0Not supported
meta.llama4-scout-17b-instruct-v1:0bedrock-runtimeus.meta.llama4-scout-17b-instruct-v1:0Not supported
nvidia.nemotron-nano-12b-v2bedrock-runtimeus-gov.nvidia.nemotron-nano-12b-v2Not supported
nvidia.nemotron-nano-9b-v2bedrock-runtimeus-gov.nvidia.nemotron-nano-9b-v2Not supported

Sources: DeepSeek-R1 model card , Llama 3.1 70B Instruct model card , Llama 3.1 8B Instruct model card , Llama 3.3 70B Instruct model card , Llama 4 Maverick model card , Llama 4 Scout model card , Nemotron Nano 12B v2 model card , Nemotron Nano 9B v2 model card , Llama 3 70B Instruct model card , Llama 3 8B Instruct model card , DeepSeek-V3.1 model card , Kimi K2 Thinking model card , Qwen3-Coder-30B model card , Qwen3 Coder 480B model card , GLM 4.7 model card , GLM 4.7 Flash model card , Inference profiles with limited model selection , checked November 3, 2026.

Same-family models AWS did not name

The legacy page says to migrate to an Active model. It does not name the id. Models at a glance still lists newer names in some of these families. The cards below say Active and EOL date N/A. AWS did not name them as replacements. They are not stored on these rows.

The Gemma 4 E2B card says: "Gemma 4 models are available only on the bedrock-mantle endpoint." The Gemma 4 31B and Gemma 4 26B-A4B cards list a bedrock-mantle row and do not list a bedrock-runtime row. A bedrock-runtime Converse call cannot send those ids.

Models at a glance still names Llama 3.2 and Llama 3.1 405B. The legacy page lists those ids under models that have reached EOL, with EOL date July 7, 2026. They are not Active replacements for the March 30, 2027 Llama rows. This guide does not name a Llama id to send.

The Kimi K2.5 card says the geo inference ID and the global inference ID are Not supported. The Kimi K3 card prints us.moonshotai.kimi-k3 in the commercial AWS Regions, in.moonshotai.kimi-k3 in the India Regions, and global.moonshotai.kimi-k3. The GLM 5 card says geo and global are Not supported. The GLM 5.3 card prints model ID zai.glm-5.3, says the in-region endpoint URL is Not supported, and prints geo id us.zai.glm-5.3 and global id global.zai.glm-5.3.

Active ids on Bedrock model cards. AWS did not name these as replacements.
Retiring modelsActive id on a model cardWhat the card says
DeepSeek-R1 and DeepSeek-V3.1deepseek.v3.2Active. EOL date N/A. Geo and global are Not supported.
Gemma 3 4B IT, 12B IT, and 27B PTgoogle.gemma-4-31b, google.gemma-4-26b-a4b, google.gemma-4-e2bActive. EOL date N/A. bedrock-mantle only.
Llama 3, 3.1, 3.3, and Llama 4no official replacementNo newer Active Llama id on the legacy page or on Models at a glance.
MiniMax M2 and MiniMax M2.1minimax.minimax-m2.5Active. EOL date N/A. Geo and global are Not supported.
Mistral 7B Instruct and Mixtral 8x7B Instructmistral.mistral-large-3-675b-instruct, mistral.ministral-3-14b-instruct, mistral.ministral-3-8b-instruct, mistral.ministral-3-3b-instruct, mistral.magistral-small-2509Active. EOL date N/A. Newer Mistral text ids. AWS did not name them.
Devstral 2 123B and both Voxtral idsno official replacementModels at a glance does not list a newer Devstral id or a newer Voxtral id.
Kimi K2 Thinkingmoonshotai.kimi-k2.5, moonshotai.kimi-k3Active. EOL date N/A.
Nemotron Nano 9B v2 and 12B v2nvidia.nemotron-nano-3-30b, nvidia.nemotron-super-3-120bActive. EOL date N/A.
Qwen3 Coder 30B and 480Bqwen.qwen3-coder-nextActive. EOL date N/A. Geo and global are Not supported.
GLM 4.7 and GLM 4.7 Flashzai.glm-5, zai.glm-5.3Active. EOL date N/A. Read the GLM 5.3 inference ids before you send a bare id.

Sources: Models at a glance , Amazon Bedrock model lifecycle (legacy) , DeepSeek V3.2 model card , Gemma 4 31B model card , Gemma 4 26B-A4B model card , Gemma 4 E2B model card , MiniMax M2.5 model card , Mistral Large 3 model card , Ministral 14B 3.0 model card , Ministral 3 8B model card , Ministral 3B model card , Magistral Small 2509 model card , Kimi K2.5 model card , Kimi K3 model card , Nemotron Nano 3 30B model card , Nemotron Super 3 120B model card , Qwen3 Coder Next model card , GLM 5 model card , GLM 5.3 model card , checked November 3, 2026.

Change the Converse modelId

The DeepSeek-R1 card's Converse sample creates a bedrock-runtime client with region_name us-east-1 and sends modelId us.deepseek.r1-v1:0. The sample below changes that argument to deepseek.v3.2. The DeepSeek V3.2 card lists that id on bedrock-runtime and says the model lifecycle is Active. AWS did not name it as the replacement for deepseek.r1-v1:0 or for any other id in the table above.

The V3.2 card says the geo inference ID is Not supported. The sample does not add a us. prefix. Do not send us.deepseek.v3.2. That id is not on the card.

Use the same modelId field for the other retiring ids. Pick the Active id you will actually call. Gemma 4 ids are on bedrock-mantle, so they do not belong in this bedrock-runtime client.

boto3 Converse. modelId changed from the DeepSeek-R1 card sample. AWS did not name this replacement.

import boto3

client = boto3.client("bedrock-runtime", region_name="us-east-1")
response = client.converse(
    modelId="deepseek.v3.2",
    messages=[{"role": "user", "content": [{"text": "Hello"}]}],
)

Sources: DeepSeek-R1 model card , DeepSeek V3.2 model card , Amazon Bedrock model lifecycle (legacy) , checked November 3, 2026.

Find the model ids in your code

Search the repository for the bare ids and for the geo ids in the table above. 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. 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. The batch page for this date is /shutdowns/aws-bedrock-2027-03-30/.

ripgrep, bare ids plus the geo ids the cards print

rg -n -w -e 'deepseek.r1-v1:0' -e 'deepseek.v3-v1:0' -e 'deepseek.v3.1' -e 'google.gemma-3-12b-it' -e 'google.gemma-3-27b-it' -e 'google.gemma-3-4b-it' -e 'meta.llama3-1-70b-instruct-v1:0' -e 'meta.llama3-1-8b-instruct-v1:0' -e 'meta.llama3-3-70b-instruct-v1:0' -e 'meta.llama3-70b-instruct-v1:0' -e 'meta.llama3-8b-instruct-v1:0' -e 'meta.llama4-maverick-17b-instruct-v1:0' -e 'meta.llama4-scout-17b-instruct-v1:0' -e 'minimax.minimax-m2' -e 'minimax.minimax-m2.1' -e 'mistral.devstral-2-123b' -e 'mistral.mistral-7b-instruct-v0:2' -e 'mistral.mixtral-8x7b-instruct-v0:1' -e 'mistral.voxtral-mini-3b-2507' -e 'mistral.voxtral-small-24b-2507' -e 'moonshot.kimi-k2-thinking' -e 'moonshotai.kimi-k2-thinking' -e 'nvidia.nemotron-nano-12b-v2' -e 'nvidia.nemotron-nano-9b-v2' -e 'qwen.qwen3-coder-30b-a3b-instruct' -e 'qwen.qwen3-coder-30b-a3b-v1:0' -e 'qwen.qwen3-coder-480b-a35b-instruct' -e 'qwen.qwen3-coder-480b-a35b-v1:0' -e 'zai.glm-4.7' -e 'zai.glm-4.7-flash' -e 'us.deepseek.r1-v1:0' -e 'us.meta.llama3-1-70b-instruct-v1:0' -e 'us.meta.llama3-1-8b-instruct-v1:0' -e 'us.meta.llama3-3-70b-instruct-v1:0' -e 'us.meta.llama4-maverick-17b-instruct-v1:0' -e 'us.meta.llama4-scout-17b-instruct-v1:0' -e 'us-gov.nvidia.nemotron-nano-12b-v2' -e 'us-gov.nvidia.nemotron-nano-9b-v2'

Sources: Amazon Bedrock model lifecycle (legacy) , DeepSeek-R1 model card , checked November 3, 2026.

Related SunsetDiff pages

All guides

Questions

Which Bedrock model ids reach end of life on March 30, 2027?

The dataset lists 30 ids with shutdown date 2027-03-30: deepseek.r1-v1:0, deepseek.v3-v1:0, deepseek.v3.1, google.gemma-3-12b-it, google.gemma-3-27b-it, google.gemma-3-4b-it, meta.llama3-1-70b-instruct-v1:0, meta.llama3-1-8b-instruct-v1:0, meta.llama3-3-70b-instruct-v1:0, meta.llama3-70b-instruct-v1:0, meta.llama3-8b-instruct-v1:0, meta.llama4-maverick-17b-instruct-v1:0, meta.llama4-scout-17b-instruct-v1:0, minimax.minimax-m2, minimax.minimax-m2.1, mistral.devstral-2-123b, mistral.mistral-7b-instruct-v0:2, mistral.mixtral-8x7b-instruct-v0:1, mistral.voxtral-mini-3b-2507, mistral.voxtral-small-24b-2507, moonshot.kimi-k2-thinking, moonshotai.kimi-k2-thinking, nvidia.nemotron-nano-12b-v2, nvidia.nemotron-nano-9b-v2, qwen.qwen3-coder-30b-a3b-instruct, qwen.qwen3-coder-30b-a3b-v1:0, qwen.qwen3-coder-480b-a35b-instruct, qwen.qwen3-coder-480b-a35b-v1:0, zai.glm-4.7, zai.glm-4.7-flash. The legacy lifecycle page lists each one as Legacy, with legacy date September 30, 2026 and EOL date March 30, 2027.

Does March 30, 2027 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 is different for each model. Call ListFoundationModels or GetFoundationModel in the Region you use and read modelLifecycle.

What is the official recommended replacement?

no official replacement. The stored replacements list is empty on every row in this guide. 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. Same-family Active ids on other model cards are not a recommendation from that page.

What happens to a call after March 30, 2027?

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 does not print an exception name. The model cards checked for these ids do not print one either. Migration will not happen automatically.

Which cross-Region ids does AWS print for these models?

The DeepSeek-R1 card prints us.deepseek.r1-v1:0. The Llama 3.1 70B, Llama 3.1 8B, Llama 3.3 70B, Llama 4 Maverick, and Llama 4 Scout cards print a us. geo id and say the global inference ID is Not supported. The two Nemotron Nano cards print us-gov.nvidia.nemotron-nano-12b-v2 and us-gov.nvidia.nemotron-nano-9b-v2 on bedrock-runtime. No card in this set prints an eu. id.

Can I keep a us. prefix on the new modelId?

Only when the new model's card prints that prefixed id. The DeepSeek V3.2 card says the geo inference ID is Not supported, so the Converse sample on this page sends deepseek.v3.2 with no prefix. The DeepSeek-R1 card sample sends us.deepseek.r1-v1:0. Replacing the bare id and leaving the prefix does not finish the change.

What does To be announced mean here?

The legacy table prints To be announced in the public extended access start date column for every id in this guide. 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 start date or a price for these ids.

More guides

Deprecation alerts

We email you before models shut down. Unsubscribe anytime.

Deprecation alert signup
Providers (optional)