claude-code - 💡(How to fix) Fix AWS Bedrock / SSO Authentication for Claude.ai Desktop & Web App [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56053Fetched 2026-05-05 05:59:26
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
1
Participants
Timeline (top)
labeled ×2unlabeled ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

As an enterprise user, I access Claude through AWS Bedrock using my organization's AWS SSO (Single Sign-On) credentials. This works well for Claude Code, but the Claude.ai desktop and web applications have no equivalent — they require a separate Anthropic account and subscription.

The gap: My organization manages Claude access through AWS IAM and Bedrock. Individual team members authenticate via AWS SSO and are billed centrally through our AWS account. There is no way to bring that same identity and billing relationship into the claude.ai chat interface.

The request: Allow the Claude.ai desktop and web app to be configured with an AWS Bedrock endpoint and AWS credentials (including SSO/IAM roles), so enterprise users can access the full claude.ai experience — conversations, projects, artifacts — without requiring a separate Anthropic account or subscription.

This would mirror how many enterprise tools support multiple identity providers. AWS Bedrock is already the approved, centrally-managed path for Claude in our organization; the chat interface should be able to follow that same path.

Proposed Solution

As an enterprise user, I access Claude through AWS Bedrock using my organization's AWS SSO (Single Sign-On) credentials. This works well for Claude Code, but the Claude.ai desktop and web applications have no equivalent — they require a separate Anthropic account and subscription.

The gap: My organization manages Claude access through AWS IAM and Bedrock. Individual team members authenticate via AWS SSO and are billed centrally through our AWS account. There is no way to bring that same identity and billing relationship into the claude.ai chat interface.

The request: Allow the Claude.ai desktop and web app to be configured with an AWS Bedrock endpoint and AWS credentials (including SSO/IAM roles), so enterprise users can access the full claude.ai experience — conversations, projects, artifacts — without requiring a separate Anthropic account or subscription.

This would mirror how many enterprise tools support multiple identity providers. AWS Bedrock is already the approved, centrally-managed path for Claude in our organization; the chat interface should be able to follow that same path.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

To address the issue, the Claude.ai desktop and web applications should be updated to support authentication with AWS Bedrock endpoints and AWS credentials, including SSO/IAM roles.

Guidance

  • Investigate existing authentication mechanisms in Claude Code that utilize AWS SSO credentials to identify potential pathways for integration with the Claude.ai desktop and web applications.
  • Research industry standards for supporting multiple identity providers in enterprise tools to inform the design of the proposed solution.
  • Consider the security and billing implications of allowing AWS Bedrock authentication for the Claude.ai chat interface, ensuring that it aligns with the organization's centrally managed access and billing processes.
  • Evaluate the feasibility of implementing this feature as a configuration option within the Claude.ai applications, allowing enterprise users to input their AWS Bedrock endpoint and credentials.

Notes

The implementation details and technical requirements for integrating AWS Bedrock authentication with the Claude.ai desktop and web applications are not specified in the issue, and thus, a precise code example or step-by-step technical guide cannot be provided.

Recommendation

Apply workaround: While a full integration might require significant development, exploring temporary workarounds such as single sign-on solutions that can bridge AWS SSO with the Claude.ai applications could provide an interim solution, enhancing productivity for enterprise users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING