{"version":"2.1.232","anchor":"invalid-aws-region-environment-values-are-reported-instead-o","canonical_anchor":"invalid-aws-region-environment-values-are-reported-instead-o","heading":"Invalid AWS region environment values are reported instead of hidden","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/invalid-aws-region-environment-values-are-reported-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Invalid AWS region environment values are reported instead of hidden\n\nAn invalid AWS_REGION is now reported as invalid rather than silently treated as default.\n\n**What**\n\nWhen `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`.\n\n**Evidence**\n\n`env-invalid`\n\n- Area: Bedrock\n- Names: `AWS_REGION`, `AWS_DEFAULT_REGION`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}