Answer: Remove the `awsAuthRefresh` setting from your settings file, and if your network environment interferes with automatic browser-based SSO flows, use `aws sso login` manually before starting Claude Code instead of relying on `awsAuthRefresh`. Status: Confirmed Entry: tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting Revision: 2 Digest: sha256:baf471d18063f742 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:03:14Z Last changed: 2026-11-18T12:13:42Z (alternative: — → use `aws sso login` manually before starting Claude Code) Last verified: 2026-11-20T12:17:57Z Next check: 2026-11-21T12:17:57Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of fix | remove the `awsAuthRefresh` setting | [1] | 2026-11-20 cause | corporate VPNs or TLS inspection proxies interrupt the SSO browser flow | [1] | 2026-11-20 alternative | use `aws sso login` manually before starting Claude Code | [1] | 2026-11-20 Sources: [1] Anthropic. "Claude Code on Amazon Bedrock". https://code.claude.com/docs/en/amazon-bedrock.md Role: primary. Accessed: 2026-11-20T12:17:57Z Quote: "remove the `awsAuthRefresh` setting from your [settings file]" (Supports: fix) Quote: "The loop can occur when corporate VPNs or TLS inspection proxies interrupt the SSO browser flow." (Supports: cause) Quote: "use `aws sso login` manually before starting Claude Code instead of relying on `awsAuthRefresh`" (Supports: alternative) Published: 2026-11-20T03:13:32Z Snapshot SHA-256: bf97c0351fbb18b8a8435014287aeb76bc77fa1ba950656d3bbc83d49fed5f7f (captured 2026-11-17T12:22:20Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T12:22:21Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:17:57Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:17:57Z Last attempt: 2026-11-20T12:17:57Z Notes and limitations: Extracted automatically from a single official source (section "Authentication loop with SSO and corporate proxies"). Related: https://latestn.com/tool/claude-code/troubleshooting/status-line-troubleshooting Why is my Claude Code status line not appearing or showing empty values? https://latestn.com/tool/claude-code/troubleshooting/structured-output-error-handling What happens when Claude Code structured output validation fails and how is it handled? https://latestn.com/tool/claude-code/troubleshooting/structured-output-none Why does the Claude Code Agent SDK return a successful result but structured_output is None? https://latestn.com/tool/claude-code/troubleshooting/simulator-pane-not-opening Why doesn't the iOS Simulator pane open when Claude runs my app in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/skill-not-triggering Why is my Claude Code skill not triggering? https://latestn.com/tool/claude-code/troubleshooting/slack-repo-not-showing Why isn't my repository showing in Claude Code in Slack? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:13:42Z | changed | alternative: — → use `aws sso login` manually before starting Claude Code | [1] 2026-11-18T12:13:42Z | changed | cause: — → corporate VPNs or TLS inspection proxies interrupt the SSO browser flow | [1] 2026-11-18T12:13:42Z | changed | fix: — → remove the `awsAuthRefresh` setting | [1] 2026-11-18T12:13:42Z | changed | Cause: corporate VPNs or TLS inspection proxies interrupt the SSO browser flow → — | [1] 2026-11-18T12:13:42Z | changed | Alternative: use `aws sso login` manually before starting Claude Code → — | [1] 2026-11-18T12:13:42Z | changed | Fix: remove the `awsAuthRefresh` setting → — | [1] 2026-11-13T03:03:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot authentication loops with SSO and corporate proxies in Claude Code on Amazon Bedrock? Revision 2, last verified 2026-11-20T12:17:57Z. https://latestn.com/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting (accessed 2026-11-21T09:56:44Z). @misc{LatestN_tool_claude_code_troubleshooting_sso_auth_loop_troubleshooting_r2, title = {How do I troubleshoot authentication loops with SSO and corporate proxies in Claude Code on Amazon Bedrock?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting}}, note = {Revision 2; digest sha256:baf471d18063f742; last verified 2026-11-20T12:17:57Z; accessed 2026-11-21T09:56:44Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/sso-auth-loop-troubleshooting