Bedrock no longer fails when neither a region nor a base URL is…

Bedrock no longer fails when neither a region nor a base URL is set

Bedrock no longer refuses to start when no region or base URL is configured.

You'll noticeTier: how much it should matter to you

3Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

BedrockArea: what it touches

Bug FixesKind: in v2.1.228, 11 Aug 26

Bug FixesSection of the release

What

Using the AWS Bedrock provider without AWS_REGION, AWS_DEFAULT_REGION or ANTHROPIC_AWS_BASE_URL previously threw "No AWS region or base URL found." Construction now continues with the base URL left unset.

Evidence

ANTHROPIC_AWS_BASE_URL

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

Read from

Names in the bundleAWS_REGIONANTHROPIC_AWS_BASE_URL

See this entry in the whole of v2.1.228 →

The build it came inv2.1.228

11 Aug 2026 · 245 entries, this one is #141.

Use it now22
You'll notice117
Nothing to try yet28
Under the hood78

Either side of it

v2.1.227Older
v2.1.229Newer

Open the release →

Names in this entry

envAWS_REGION
Bedrock no longer refuses to start when no region or base URL is configured.
envAWS_DEFAULT_REGION
Bedrock no longer refuses to start when no region or base URL is configured.
envANTHROPIC_AWS_BASE_URL
Override the Claude Platform on AWS endpoint URL. Use for custom regions or when routing through an LLM gateway. Defaults to https://aws-external-anthropic.{region}.api.aws. Claude Code resolves the region with the same precedence as on Amazon Bedrock

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.232 Invalid AWS region environment values are reported instead of hidden
Both mention region bedrock
v2.1.232 Invalid AWS region variable is called out by name
Both mention region bedrock
v2.1.232 A malformed AWS region env var is now ignored and reported
Both mention region bedrock