{"version":"2.1.300","anchor":"aws-auth-refresh-refused-when-a-guard-is-set","canonical_anchor":"aws-auth-refresh-refused-when-a-guard-is-set","heading":"AWS sign-in refresh command can now be skipped in some situations","tier":"notice","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/aws-auth-refresh-refused-when-a-guard-is-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### AWS sign-in refresh command can now be skipped in some situations\n\nClaude Code now skips your AWS auth refresh command in certain situations, reports it as failed and logs a reason\n\n**Unclear.** It is not clear which situations stop the AWS refresh command from running.\n\n**What**\n\nThe `awsAuthRefresh` setting holds a command Claude Code runs to refresh your AWS credentials. Before, Claude Code always ran it when a refresh was needed.\n\nThere is now a condition under which Claude Code does not run the command. It reports the refresh as failed straight away and logs why.\n\n**Why**\n\nIf you rely on `awsAuthRefresh`, a refresh may now fail without your command running. Check the log message when that happens.\n\n- Area: Auth\n- Names: `awsAuthRefresh`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}