Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude for Excel (Bedrock direct) selects `us.` inference profile when manifest `aws_region` is `eu-west-1`, causing 400/404 at `bedrock-runtime.eu-west-1.amazonaws.com`

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…

Error Message

Claude for Office connection failed (Bedrock) Build: *****

400 The provided model identifier is invalid.

Request: aws_role_arn: arn:aws:iam::*********:role/ClaudeBedrockAccess aws_region: eu-west-1

Manifest params: m: unified-1.0.0.12 aws_role_arn: arn:aws:iam::********:role/ClaudeBedrockAccess aws_region: eu-west-1 entra_sso: 1 et:

Bootstrap response: (not called)

Raw error: 400 The provided model identifier is invalid.

Root Cause

The root cause appears to be that the add-in's model selection logic is not region-aware: it picks a us.-prefixed inference profile regardless of the configured aws_region.

Code Example

https://bedrock-runtime.eu-west-1.amazonaws.com/model/us.anthropic.claude-opus-4-7/invoke

---

Claude for Office connection failed (Bedrock)
Build: *****

400 The provided model identifier is invalid.

Request:
  aws_role_arn: arn:aws:iam::*********:role/ClaudeBedrockAccess
  aws_region: eu-west-1

Manifest params:
  m: unified-1.0.0.12
  aws_role_arn: arn:aws:iam::********:role/ClaudeBedrockAccess
  aws_region: eu-west-1
  entra_sso: 1
  et: 

Bootstrap response:
  (not called)

Raw error:
400 The provided model identifier is invalid.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When the claude-in-office manifest is provisioned with aws_region: eu-west-1 for the Bedrock direct path, the add-in constructs invoke URLs of the form:

https://bedrock-runtime.eu-west-1.amazonaws.com/model/us.anthropic.claude-opus-4-7/invoke

This is an invalid combination. The us. cross-region inference profile only exists in and routes to us-east-1, us-east-2, and us-west-2. It is not resolvable from a bedrock-runtime.eu-west-1.amazonaws.com endpoint, so every request fails.

The root cause appears to be that the add-in's model selection logic is not region-aware: it picks a us.-prefixed inference profile regardless of the configured aws_region.

Why admins cannot work around this

Per the third-party platforms documentation and the claude-in-office manifest spec, admins can configure aws_region but cannot pin a specific inference profile ID. The add-in discovers and selects the model at runtime. That means this bug cannot be worked around through manifest configuration — it requires a code fix.

What Should Happen?

When aws_region is an EU region, the add-in should select a compatible profile:

  • An eu.-prefixed geographic CRIS profile if one exists for the target model (e.g., eu.anthropic.claude-opus-4-6-v1 for Opus 4.6), or
  • A global.-prefixed profile (e.g., global.anthropic.claude-opus-4-7) when no eu. profile exists and the source region supports global CRIS (eu-west-1 does).

Symmetrically for apac. / APAC regions.

Error Messages/Logs

Claude for Office connection failed (Bedrock)
Build: *****

400 The provided model identifier is invalid.

Request:
  aws_role_arn: arn:aws:iam::*********:role/ClaudeBedrockAccess
  aws_region: eu-west-1

Manifest params:
  m: unified-1.0.0.12
  aws_role_arn: arn:aws:iam::********:role/ClaudeBedrockAccess
  aws_region: eu-west-1
  entra_sso: 1
  et: 

Bootstrap response:
  (not called)

Raw error:
400 The provided model identifier is invalid.

Steps to Reproduce

  1. Run /claude-in-office:setup and configure the Bedrock direct path with aws_region: eu-west-1.
  2. Ensure the signed-in AWS role has access to eu. and/or global. inference profiles in eu-west-1 (verified working via AWS CLI bedrock-runtime invoke-model).
  3. Deploy the manifest and open Claude for Excel.
  4. Sign in via Entra ID.
  5. Any prompt fails with an invocation error against https://bedrock-runtime.eu-west-1.amazonaws.com/model/us.anthropic.claude-opus-4-7/invoke.

Expected Behavior

The add-in selects an inference profile whose source-region list includes the configured aws_region, and successfully invokes the model.

Actual Behavior

The add-in selects us.anthropic.claude-opus-4-7 (or similar us.-prefixed profile) and sends it to the eu-west-1 endpoint, resulting in a 400/404.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.113

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The add-in's model selection logic needs to be updated to be region-aware, selecting compatible profiles based on the configured aws_region.

Guidance

  • The issue arises from the add-in selecting a us.-prefixed inference profile regardless of the aws_region, which is not resolvable from a bedrock-runtime.eu-west-1.amazonaws.com endpoint.
  • To fix this, the add-in's model selection logic should be modified to choose a compatible profile based on the aws_region, such as an eu.-prefixed profile for EU regions or a global.-prefixed profile if no regional profile exists.
  • The selection logic should consider the source-region list of available inference profiles to ensure compatibility with the configured aws_region.
  • Admins cannot work around this issue through manifest configuration, so a code fix is required.

Example

No code example is provided as the issue does not include specific code snippets, but the model selection logic should be updated to consider the aws_region when choosing an inference profile.

Notes

The fix requires updating the add-in's model selection logic to be region-aware, which may involve modifying the code to handle different regions and their corresponding inference profiles.

Recommendation

Apply a workaround is not feasible in this case, as the issue requires a code fix to update the model selection logic. The recommendation is to update the code to make the model selection logic region-aware.

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…
#parallel task#integration issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude for Excel (Bedrock direct) selects `us.` inference profile when manifest `aws_region` is `eu-west-1`, causing 400/404 at `bedrock-runtime.eu-west-1.amazonaws.com`