[DOCS] Documentation inconsistency: AWS Bedrock setup requires `AWS_REGION` env var despite `aws configure` step

Resolved 💬 3 comments Opened Jan 18, 2026 by coygeek Closed Feb 28, 2026

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/amazon-bedrock

Section/Topic

The "Setup" section, specifically the relationship between step "2. Configure AWS credentials" (Option A) and step "3. Configure Claude Code".

Current Documentation

Step 2, Option A suggests:

Option A: AWS CLI configuration ``bash aws configure ``

Step 3 then states:

AWS_REGION is a required environment variable. Claude Code does not read from the .aws config file for this setting.

What's Wrong or Missing?

The documentation gives conflicting guidance regarding AWS region configuration.

  1. In Step 2, users are told to run aws configure. Standard behavior for this command involves inputting an AWS Region, which is saved to ~/.aws/config. Users familiar with the AWS SDK expect tools to read the region from this file.
  2. However, Step 3 explicitly invalidates that configuration by stating Claude Code ignores the .aws config file for the region setting and mandates an environment variable instead.

This renders the region configuration performed in Step 2 useless and creates confusion for users who believe they have already configured the region via the CLI.

Suggested Improvement

Clarify in Step 2 that while aws configure handles credentials, the region input provided there will not be used by Claude Code.

Alternatively, modify the note in Step 3 to explicitly reference the previous step to prevent confusion. For example:

Note: Even if you specified a region during aws configure in the previous step, you must still export the AWS_REGION environment variable below. Claude Code does not read the region from the .aws config file.

Impact

High - Prevents users from using a feature

Additional Context

  • Standard AWS SDK behavior usually respects the [default] profile region in ~/.aws/config if no environment variable is set. The deviation from this standard behavior makes the documentation contradiction more jarring for experienced AWS users.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗