{"version":"2.1.232","anchor":"invalid-aws-region-variable-is-called-out-by-name","canonical_anchor":"invalid-aws-region-variable-is-called-out-by-name","heading":"Invalid AWS region variable is called out by name","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/invalid-aws-region-variable-is-called-out-by-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Invalid AWS region variable is called out by name\n\nOn Bedrock, an unusable AWS region variable is now named so you can fix or unset it.\n\n**What**\n\nOn Bedrock, if `AWS_REGION` or `AWS_DEFAULT_REGION` holds a value Claude Code cannot use, the region display now says the variable was invalid and ignored and tells you to fix or unset it, rather than showing the generic hint to set a region.\n\n**Details**\n\n- The AWS client path now waits for the region to resolve and passes it explicitly, so the label and the region actually used agree.\n\n**Evidence**\n\n`region env var invalid, ignored; fix or unset AWS_REGION \/ AWS_DEFAULT_REGION`\n\n- Area: Bedrock\n- Names: `AWS_REGION`, `AWS_DEFAULT_REGION`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}