[FEATURE] separate AWS profiles for Bedrock model calls and for AWS API calls

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

I always am operating in two AWS accounts where the first account is always the same (my Bedrock account where my company bills Bedrock) and the second account will change depending on the project I am working on.

Currently, Claude Code lets me set AWS_PROFILE in my global env settings which is then used for Bedrock auth and also for any AWS API calls that are made within Claude. Most of my work in AWS is read-only, and my IAM role within my Bedrock account is limited to Bedrock, so these API calls just fail due to insufficient permissions or the resources not existing. However, I could see this being an issue for folks doing work that is write-based and inadvertently making AWS calls in an unintended account. At the very least, it means workflows in CC need to be heavily adjusted to accommodate for the fact that Claude Code will use the Bedrock AWS_PROFILE for all calls.

There's a good, concise problem statement here: https://github.com/anthropics/claude-code/issues/148#issuecomment-2902861830

Proposed Solution

I'd like to be able to set two AWS profile settings, one for Bedrock model calls and one for everything else. An example end-state configuration file might look like:

{
  "awsAuthRefresh": "aws sso login --profile BedrockProfile",
  "env": {
    "CLAUDE_CODE_USE_BEDROCK": "true",
    "AWS_REGION": "us-west-2",
    "CLAUDE_CODE_AWS_PROFILE": "BedrockProfile",
    "AWS_PROFILE": "WorkProfile"
  },
  "model": "us.anthropic.claude-opus-4-5-20251101-v1:0",
}

where the CLAUDE_CODE_AWS_PROFILE is what is used for making model calls, and where the AWS_PROFILE is used for all bash commands/propagates to the environment in which bash commands are run (so downstream processes pick up this AWS profile in the env vars).

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_