Unclear It is not clear whether an AWS_PROFILE set somewhere other than your shell, such as in Claude Code settings, now counts for this check.
What
AWS_PROFILE names which AWS account profile to use, for example with Amazon Bedrock. Claude Code now reads it, and related AWS values, through a helper instead of straight from its own environment.
awsAuthRefresh: the watcher that decides when your own credential-refresh command should run now readsAWS_PROFILEthrough the helper.- Credential setup check: the check of your AWS credential configuration also reads
AWS_PROFILEthrough the helper. - New AWS helpers: new code reads
AWS_PROFILEandAWS_REGIONfrom the environment values in your settings, and loadsendpoint_url, FIPS and dualstack options from the AWS config files for that profile, for Bedrock and AWS STS (the AWS service that hands out temporary credentials).AWS_ENDPOINT_URLalso appears.
Why
The members suggest an AWS_PROFILE or AWS_REGION set in Claude Code settings, not only in your shell, may now be the one that is used and that triggers a credential refresh. If you use Bedrock with custom endpoints, FIPS or dualstack options in your AWS config, those may now be picked up for the chosen profile.
Names in the bundleawsAuthRefreshAWS_PROFILE
Documented inclaude-code/amazon-bedrock
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether an `AWS_PROFILE` set somewhere other than your shell, such as in Claude Code settings, now counts for this check.
Anthropic's release notes agree
Fixed the awsAuthRefresh or gcpAuthRefresh command sometimes running twice for one request when three or more sessions needed a fresh…