What
The awsAuthRefresh setting, which runs a command to refresh AWS credentials, now takes either the old shell string or a structured {file, args, env} form that avoids a shell.
Details
- For the structured form the executable is resolved and rejected unless it sits in a safe directory: "AWS auth refresh: executable not found in a safe directory".
.cmdand.battargets are quoted and run through a shell.- Failure and timeout messages now name the command that was run instead of pointing at the settings key.
Evidence
AWS auth refresh: executable not found in a safe directory
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleawsAuthRefresh
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Claude Code on Amazon Bedrock touched a line naming awsAuthRefresh after this was published.
Mantle is an Amazon Bedrock endpoint that serves Claude models through the native Anthropic API shape rather than the Amazon Bedrock Invoke API. It uses the same [AWS credentials](#2-configure-aws-credentials), [IAM permissions](#iam-confi…amazon-bedrock see the edit
Confirmed since
Anthropic's documentation has since written up awsAuthRefresh, on All settings.
| Read from the highest-priority source only | Reads the key only from the highest-priority source that carries a policy key, so a lower source's value is ignored even when the highest source sets none | [`apiKeyHelper`](#apikeyhelper), [`…settings-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up awsAuthRefresh, on All settings.