[FEATURE] Dedicated AWS profile config for Bedrock requests

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When using Claude Code with AWS Bedrock, the only supported way to isolate the Bedrock AWS profile from the shell's active AWS_PROFILE is to set AWS_PROFILE. This works, but it has a side-effect: it propagates the Bedrock-specific AWS profile to bash commands.

Engineers often work across multiple AWS accounts simultaneously - for example:

• AWS account A: Bedrock billing account (the one Claude Code should use)
• AWS account B: active dev/infra account (the one all other CLI tools like aws, terraform, kubectl should use).

This issue was raised in #148 and closed for inactivity.

Proposed Solution

introducing additional env variable like CLAUDE_CODE_AWS_PROFILE or CLAUDE_CODE_AWS_PROFILE_BEDROCK which for Claude Code takes precedence over AWS_PROFILE

Alternative Solutions

No workaround exists

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_