Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.232entry #205

Claude Code v2.1.232 ·

Invalid AWS region environment values are reported instead of hidden

An invalid AWS_REGION is now reported as invalid rather than silently treated as default.

You'll notice Improvements
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
BedrockArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What

When AWS_REGION or AWS_DEFAULT_REGION is set to something that does not validate, Bedrock region detection now reports the source as env-invalid rather than pretending it used the default, and falls back to us-east-1.

Evidence

env-invalid

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleAWS_REGIONAWS_DEFAULT_REGION
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up AWS_REGION, on Claude Code on Amazon Bedrock. * You only need to set `AWS_REGION` to override your AWS profile's region or when your profile has no region. Claude Code resolves the region in this order: amazon-bedrock see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up AWS_REGION, on Claude Code on Amazon Bedrock.

See this entry in the whole of v2.1.232 →

Feedback