[FEATURE] Support Amazon Bedrock as backend for Claude Desktop / Cowork

+1, I'd really like to use Claude Code Desktop

My org can't use desktop for work without AWS Bedrock billing integration and that's disappointing given the difficulty of use/absence in CC CLI of some useful cowork agentic features

+1 - enterprises will be using this a lot, and this is an issue that needs accommodating for

Google Vertex and Azure AI are worth considering as well, there are a few enterprises who are all in on GCP or Azure that might go for this

I found this issue very annoying. Especially when you have to select AWS or GCP as the only possible solution if you want to fulfill GDPR?
So 2/3 of the Enterprise features are useless for european companies?

+1 this would be a game changer. Currently heavily invested in Claude Code and AWS Bedrock

I am currently using claude code with bedrock via local settings file. This feature would be very useful at my organization!

For my institution it would really be a game changer. We are already starting to roll out Claude Code using Bedrock and will eventually offer it with Vertex AI. This allows us to use Claude Code since we have a BAA with both AWS and Google GCP.

+1, we are sitting on a lot of AWS credits and would love to use it for not only Claude Code CLI but also Cowork etc.

+1

+1

Our organization is currently rolling out VSCode+ClaudeCode plugin to approximate this. It's working but direct integration with Bedrock in Claude Desktop/Cowork would be a huge boon to our IT team and our CloudOps team.

+10000 - this is huge for orgs that handle PHI/PII and MUST use bedrock,vertex etc to maintain compliance.

can you just react with a thumbs up to the message above? spamming people watching this issue is extremely annoying

+1

+1 this would be huge for my company

Absolutely must have.

Glad to hear I’m not alone on this. How are you guys arriving here? I created this PR from the Claude terminal and I am just curious as to how is reaching a broad audience

+1 we NEED this

+1000

+1 - with rate limit on the desktop, can't do much in the enterprise without bedrock backend.

+1

+1

Adding: EU data residency / GDPR angle

Beyond the network policy use case discussed here, hyperscaler backend support for Cowork is also a regulatory blocker for EU enterprise adoption:

Under GDPR Art. 44–46, many EU customers require data processing within EU territory. Anthropic's DPA with EU SCCs does not satisfy the stricter requirements of:

• German public sector (BSI, DSGVO § 25 TTDSG)
• BaFin-supervised financial services
• Healthcare (§ 203 StGB, DSGVO Art. 9)
• Enterprises with Works Council agreements restricting US data transfers

Claude Code CLI already solves this (CLAUDE_CODE_USE_BEDROCK=1 + eu-central-1), but Cowork — the product for non-developer knowledge workers — has no backend config at all.

The ask: expose the same hyperscaler backend options in Cowork (via settings or MDM policy), so EU enterprise and public sector customers can use Cowork with EU-resident inference.

This is distinct from the firewall/proxy angle in the OP — the blocker here is data residency law, not network policy. Both point to the same solution.

+1

Questioning the "invalid" label

This issue is marked as invalid, but with 23+ supporting comments from enterprise organizations, this represents significant real-world demand for a feature that already exists in Claude Code CLI.

Current State Creates Fragmented Experience

What works today:

• Claude Code CLI → ✅ Full Bedrock support via CLAUDE_CODE_USE_BEDROCK=1
• VS Code extension → ✅ Bedrock support via claudeCode.environmentVariables

What's blocked:

• Claude Desktop (Chat) → ❌ No Bedrock support
• Claude Desktop (Code tab) → ❌ OAuth token overrides Bedrock config
• Cowork → ❌ No Bedrock support

Why This Matters

Multiple enterprise categories are blocked from adopting Claude Desktop/Cowork:

1. Corporate network policies - AWS endpoints allowed, claude.ai blocked
2. Regulatory compliance - EU GDPR data residency (as detailed by @sdh07)
3. Healthcare/Finance - AWS BAA required for PHI/PII (as noted by @ericnelson)
4. Procurement - Organizations with existing AWS enterprise agreements/credits

Related: Authentication Issues

The Bedrock integration in CLI itself has reliability issues - I just filed #41064 about Claude Code getting stuck when AWS credentials expire. These infrastructure gaps compound when Desktop lacks Bedrock support entirely.

Request for Anthropic Team

Given the demonstrated enterprise demand and the fact that this functionality already exists in CLI/VS Code, could you clarify:

1. Why is this marked "invalid" rather than "enhancement"?
2. Is there a technical blocker to exposing the same Bedrock config option in Desktop?
3. What's the path forward for enterprise users who need this?

The ask isn't for new functionality - it's for parity across Claude Code surfaces (CLI, VS Code, Desktop, Cowork) so enterprise users can choose their deployment model without losing access to their required authentication backend.

+1 requesting this feature.

Please don't mark this as invalid without explaining your paid users the reason why.

+1

+1

I guess the reason behind of why they are not implementing this..
https://aws.amazon.com/blogs/awsmarketplace/anthropics-claude-for-enterprise-now-available-in-aws-marketplace/

They want to push towards the "enterprise solution" from the AWS Marketplace.

I guess the reason behind of why they are not implementing this.. https://aws.amazon.com/blogs/awsmarketplace/anthropics-claude-for-enterprise-now-available-in-aws-marketplace/ They want to push towards the "enterprise solution" from the AWS Marketplace.

I did not see this. But they need a better offer for customers. Small companies might not have 20 users needing this.

+1 on this from a GovCloud user. Our customer runs on us-gov-west-1. The CLI works fine with the documented env var setup, but the desktop app silently ignores the env block in ~/.claude/settings.json — including CLAUDE_CODE_USE_BEDROCK=1, AWS_PROFILE, and AWS_REGION — and quietly falls back to Anthropic's API via OAuth. Confirmed by inspecting the spawned CLI process env (ps eww <pid>): only ANTHROPIC_BASE_URL=https://api.anthropic.com is set, no AWS vars at all.

Two asks:
Honor the env block (or add a first-class provider setting in the GUI)
Until then, warn or error when Bedrock vars are configured but will be ignored — silent fallback to Anthropic API is a compliance hazard for users who believe their traffic is staying in GovCloud

+1

+100

Please release this feature asap

+1

+1

+1

+1

+1

+1

+1

+1

+1 come one

+1

+1

+1

+1, please also support Claude Design with amazon bedrock

+1

+1

+1

👍

+1

If i had a dollar for each +1

+1

Would really appreciate if someone from Anthropic provides some inputs. We are really held back because of this.

https://aws.amazon.com/blogs/machine-learning/from-developer-desks-to-the-whole-organization-running-claude-cowork-in-amazon-bedrock/
It's in preview now

You can now enable Bedrock in Claude Code. Here is how:

1. Open Claude Desktop app and update to latest version.
2. With Claude Desktop app open, from the top menu choose _Help -> Troubleshooting -> Enable Developer Mode_
3. From the _Developer_ menu choose _Configure Third-Party Inference_
4. In the _Connection_ section choose _Bedrock_ and fill up:

AWS region (e.g. us-east-1) AWS profile name (from ~/.aws/config) Model list (e.g. global.anthropic.claude-sonnet-4-6)

1. Click _Apply locally_
2. Relaunch

Config reference - https://claude.com/docs/cowork/3p/configuration#bedrock

Claude Desktop + AWS Bedrock (SSO) Setup

Goal

Use AWS SSO (IAM Identity Center) to authenticate Claude Desktop with AWS Bedrock.

---

1) Create an AWS SSO profile

Run:

aws configure sso --profile <your-profile-name>

Fill in:

• SSO start URL: e.g. https://your-org.awsapps.com/start
• SSO region: e.g. us-east-1
• Log in via browser when prompted
• Choose your account
• Choose your role
• CLI default region: your Bedrock region (e.g. us-east-1)
• Output format: json
• Profile name: <your-profile-name> (e.g. xxxxx-xx-dev)

---

2) Verify the profile exists

aws configure list-profiles

Optional:

cat ~/.aws/config

You should see:

[profile <your-profile-name>]
sso_session = <your-profile-name>
sso_account_id = <account-id>
sso_role_name = <role-name>
region = us-east-1
output = json

---

3) Log in with SSO

aws sso login --profile <your-profile-name>

---

4) Validate credentials

aws sts get-caller-identity --profile <your-profile-name>

If this returns account info, SSO is working.

---

5) Configure Claude Desktop (Bedrock)

1. Open Claude Desktop and update to the latest version
2. From the top menu:

Help → Troubleshooting → Enable Developer Mode

1. From the Developer menu, choose:

Configure Third-Party Inference

1. In the Connection section:

• Select Bedrock
• Fill in:

• AWS region: us-east-1 (or your Bedrock region)
• AWS profile name: <your-profile-name> (from ~/.aws/config)
• Model list: e.g. global.anthropic.claude-sonnet-4-6
• Leave AWS bearer token empty
• Leave AWS config directory empty (uses ~/.aws)

1. Click Apply locally
2. Relaunch Claude Desktop

---

6) Common issues

Profile not found

aws sts get-caller-identity --profile <name>

→ error: profile not found
✔ Re-run:

aws configure sso --profile <name>

---

SSO expired

aws sso login --profile <name>

---

Bedrock access denied

Ensure your role has:

• bedrock:InvokeModel
• bedrock:InvokeModelWithResponseStream

---

Wrong region

Make sure Bedrock is available in the region you selected (commonly us-east-1 or us-west-2).

---

7) Minimal checklist

aws configure sso --profile <name>
aws sso login --profile <name>
aws sts get-caller-identity --profile <name>

Claude Desktop:

• Provider = Bedrock
• profile name = <name>
• bearer token = empty
• restart app

Hey, first of all — the Bedrock SSO integration is a really nice addition, makes enterprise setups so much smoother.

I ran into something while using it though. When Cowork spawns subagents, it seems to resolve the haiku alias to a hardcoded inference profile ID (e.g. eu.anthropic.claude-haiku-4-5-20251001-v1:0) instead of using the application inference profile ARNs I've set in inferenceModels. This causes a 403 if the IAM principal doesn't have direct access to that profile.

In the CLI there's ANTHROPIC_DEFAULT_HAIKU_MODEL for this, but I can't find an equivalent config key for 3P Desktop mode.

Is there a way to control which Bedrock inference profile is used for subagent calls? If not, would love to see a config key for this!

Thanks

Could we have a optional name tag when we use inference profile as Model ID? When we try to select the model, its hard to identify the model from the console.

<img width="1224" height="338" alt="Image" src="https://github.com/user-attachments/assets/a92df005-c984-41e5-a72f-08a4772002e5" />

_"Enable Developer Mode"_ appears to have vanished in the latest update yet my existing config works.

<img width="303" height="174" alt="Image" src="https://github.com/user-attachments/assets/64fee7f8-18c3-4a59-9aad-adb225021d9a" />

@rsack now you can directly "Configure Third-Party Inference" without the Developer Mode

As enterprise solution we might need to migrate to mistral as soon as they offer something like this