Permission denied with aws bedrock but working with aws cli

Hi,

i get the same error:

!Image

Do you have access granted to that model in the Bedrock console on AWS?

<img width="1040" alt="Image" src="https://github.com/user-attachments/assets/d4c46bd9-7080-4b44-b8de-3d4c5358263d" />

There is an approval flow for model use within Bedrock

Yes, in all us regions. As I mentioned I can use to model through aws bedrock-runtime invoke-model --model-id us.anthropic.claude-3-7-sonnet-20250219-v1:0 ... with no issues.

Two suggestions

1. Try AWS_PROFILE= and use the envvar-based creds for the account/role with permission
2. Try removing us. from the prefix of the model name

If neither of those work, I have a PR incoming that might fix it for ya.

@8enmann Thanks for the suggestion. Unsetting the profile variable and using creds directly solves the problem!

You cannot use profiles, Claude Code does not support that.

See https://github.com/anthropics/claude-code/issues/6#issuecomment-2680841040 for the initial report and work-around.

I set the following environment variables and they worked

export CLAUDE_CODE_USE_BEDROCK=1
export ANTHROPIC_MODEL='us.anthropic.claude-3-7-sonnet-20250219-v1:0'
export DISABLE_PROMPT_CACHING=1
export AWS_ACCESS_KEY_ID=YOUR ACCESS KEY
export AWS_SECRET_ACCESS_KEY=YOUR SECRET ACCESS KEY
export AWS_REGION=YOUR REGION MODEL INFERENCE ACCESS ANTHROPIC

even with the aws configure done, you need to do these environment configurations for it to work.

PS. If you use Windows, you can use Claude's code with git bash without using WSL, but you need to set up the environment variables again every time, creating a sh script that automates this helps.

#!/bin/bash

# exporting environments
export CLAUDE_CODE_USE_BEDROCK=1
export ANTHROPIC_MODEL='us.anthropic.claude-3-7-sonnet-20250219-v1:0'
export DISABLE_PROMPT_CACHING=1
export AWS_ACCESS_KEY_ID=YOUR ACCESS KEY
export AWS_SECRET_ACCESS_KEY=YOUR SECRET ACCESS KEY
export AWS_REGION=YOUR REGION MODEL INFERENCE ACCESS ANTHROPIC

echo "environments set!"

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.