[DOCS] [Amazon Bedrock] GovCloud (`us-gov-*`) regions need `us-gov.` inference-profile prefix, not the `global` prefix; `amazon-bedrock.md` does not document GovCloud at all

Open 💬 0 comments Opened Jun 12, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/amazon-bedrock

Section/Topic

The "Model selection" section of docs/en/amazon-bedrock.md, specifically the "Cross-region inference profile IDs" subsection and the inference-profile examples. The v2.1.174 changelog fixes a 400 error on GovCloud caused by deriving the wrong inference-profile prefix, but amazon-bedrock.md only documents the us. prefix and never mentions GovCloud.

Current Documentation

docs/en/amazon-bedrock.md (line 240-246) currently says:

``bash theme={null} export ANTHROPIC_DEFAULT_OPUS_MODEL='us.anthropic.claude-opus-4-8' export ANTHROPIC_DEFAULT_SONNET_MODEL='us.anthropic.claude-sonnet-4-6' export ANTHROPIC_DEFAULT_HAIKU_MODEL='us.anthropic.claude-haiku-4-5-20251001-v1:0' ` These variables use cross-region inference profile IDs (with the us.` prefix). If you use a different region prefix or application inference profiles, adjust accordingly. For current and legacy model IDs, see Models overview. See Model configuration for the full list of environment variables."

The v2.1.174 changelog entry reads:

"Fixed Bedrock GovCloud regions (us-gov-*) deriving the wrong inference profile prefix (global instead of us-gov), causing 400 errors on derived model IDs"

docs/en/amazon-bedrock.md does not contain the strings us-gov, GovCloud, or us-gov. anywhere. A search across the docs mirror confirms the same:

rg -n "us-gov|GovCloud" docs/code.claude.com/docs/en/amazon-bedrock.md
# (no matches)

What's Wrong or Missing?

A. GovCloud regions are not mentioned anywhere in `amazon-bedrock.md`

The page documents the us. prefix for cross-region inference profiles and refers users to "a different region prefix" if they use one, but does not name the GovCloud prefix (us-gov.) or explain the difference. Users in us-gov-* regions following the docs verbatim end up with us.anthropic.claude-* IDs that 400, and there is no docs path to the fix.

B. The v2.1.174 fix has no documentation trail

Before v2.1.174, a derived model ID on a GovCloud account was rewritten to use the global prefix (Bedrock's standard cross-region prefix for us-east-1/us-west-2 accounts). GovCloud requires the us-gov prefix instead. The fix swaps the prefix-derivation logic, but amazon-bedrock.md does not say which prefix applies to which region set, so a user reading the page after the fix still has no way to know which prefix to use.

C. The `<Note>` at line 246 is too vague

The current note ("If you use a different region prefix or application inference profiles, adjust accordingly") lumps GovCloud in with all other regional differences. GovCloud is a hard break (the wrong prefix produces 400 errors, not a soft fallback), and the docs need to call it out.

Suggested Improvement

Option A: Comprehensive fix

In docs/en/amazon-bedrock.md, after the us. prefix example (line 246), add a new subsection titled "Inference profile prefixes by region":

> "### Inference profile prefixes by region
>
> Bedrock uses different inference profile prefixes depending on the region set. The prefix in the ANTHROPIC_DEFAULT_*_MODEL values must match the prefix Bedrock expects for your region:
>
> | Region set | Cross-region prefix | Example model ID |
> | :--------- | :------------------ | :--------------- |
> | US commercial (us-east-1, us-west-2) | us. | us.anthropic.claude-opus-4-8 |
> | GovCloud (us-gov-east-1, us-gov-west-1) | us-gov. | us-gov.anthropic.claude-opus-4-8 |
>
> Claude Code picks the prefix from the region detected in your AWS configuration. As of v2.1.174, accounts in us-gov-* regions get the us-gov. prefix; earlier versions derived the global prefix and produced 400 errors on the resulting model IDs. If you are pinning a specific model ID instead of using a derived one, set the full ID in ANTHROPIC_DEFAULT_*_MODEL or use an application inference profile ARN to bypass prefix derivation."

In the "Pin model versions" example block (around line 240-244), add a us-gov.* example alongside the us.* example, or add a follow-up note pointing to the new subsection.

In the troubleshooting / "If your model is unavailable" sections, add a cross-reference to the new subsection for users on GovCloud who hit a 400.

Option B: Minimum fix

Add the new "Inference profile prefixes by region" subsection only. Leave the cross-references for a later pass.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/amazon-bedrock | 240-246 | "Cross-region inference profile IDs" example and note — only documents the us. prefix, never mentions us-gov. |
| https://code.claude.com/docs/en/amazon-bedrock | (table) | "Pin model versions" example shows us.anthropic.claude-opus-4-8; no us-gov.* example |
| https://code.claude.com/docs/en/model-config | 419 | Bedrock row in the per-provider table uses us.anthropic.claude-opus-4-8; no GovCloud row |
| https://code.claude.com/docs/en/env-vars | (table) | ANTHROPIC_DEFAULT_*_MODEL env-var rows cross-reference model-config.md; no GovCloud note |
| https://code.claude.com/docs/en/changelog | 17 | Sole mention of the v2.1.174 fix; no cross-references |

Total scope: 3 pages affected, plus the changelog.

Cross-references:

https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-supported.html — AWS-side documentation for inference profile prefixes; the new subsection should link here for the authoritative list
https://code.claude.com/docs/en/amazon-bedrock#startup-model-checks — startup model checks at line 297 already skip application inference profile ARNs; the new subsection should note the same exception for us-gov.* users

Version: v2.1.174 (June 12, 2026)

View original on GitHub ↗