An invalid AWS_REGION is now reported as invalid rather than silently treated as default.
What's wrong with this entry?
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.
env-invalid
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Bedrock no longer fails when neither a region nor a base URL is set
Both mention region bedrock
-
v2.1.224
ANTHROPIC_BEDROCK_REGION_PREFIXpins the Bedrock inference-profile regionBoth mention region bedrock
-
v2.1.224
Two warnings when a Bedrock region prefix cannot be confirmed
Both mention region bedrock