›_ Claude Code Issues
Claude Code Issues / #72939

[DOCS] Gateway docs omit `anthropicAws` upstream provider and new model-not-found failover behavior

Open 💬 0 comments Opened Jul 1, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/claude-apps-gateway-config

Section/Topic

  • The "### upstreams" provider list and the per-provider subsections for Bedrock, Agent Platform, Foundry, and the Anthropic API
  • The "#### Multiple upstreams" paragraph that documents what triggers failover

Current Documentation

The upstream section enumerates four providers in provider-specific subsections and lists them in the configuration example:

upstreams:
  - provider: anthropic
    # ...
  - provider: bedrock
    # ...
  - provider: vertex
    # ...
  - provider: foundry
    # ...
Failing over between cloud providers, or to the direct Anthropic API, changes which agreement, geography, and other terms govern the request.

The "Multiple upstreams" paragraph reads:

The gateway tries upstreams in order. 5xx, 429, timeouts, and missing-endpoint (501) fail over; other 4xx doesn't. 429 is per-upstream capacity, so provisioned-throughput (PT) exhaustion fails over to on-demand. An upstream that can't resolve the requested model is skipped without a network round-trip.

What's Wrong or Missing?

A. Missing anthropicAws provider

The release notes for v2.1.198 add a new provider:

Gateway: added Claude Platform on AWS (anthropicAws) as an upstream provider; model-not-found responses now advance the failover chain

The configuration reference documents anthropic, bedrock, vertex, and foundry, but does not document an anthropicAws provider. Operators who want to run the gateway in front of Claude Platform on AWS have no documented provider key to set.

B. Missing model-not-found failover detail

The same release note says model-not-found responses now advance the failover chain, but the doc still claims:

An upstream that can't resolve the requested model is skipped without a network round-trip.

That sentence documents the local model-resolution path, but the failover section does not explain the new server-response case. As of v2.1.198, when an upstream returns a model-not-found response, the gateway advances to the next upstream instead of ending the chain at that provider.

Suggested Improvement

A. Document the anthropicAws upstream

Add a subsection alongside the existing per-provider blocks. Use the same shape as bedrock:

upstreams:
  - name: anthropic-aws
    provider: anthropicAws
    region: us-east-1
    auth: {}

The block should reference the existing Claude Platform on AWS docs page for the workspace-side authentication and IAM setup, and explain that the provider routes inference to Anthropic through the same AWS credentials surface as Claude Platform on AWS rather than the Bedrock Invoke API.

Add anthropicAws to the provider list in the upstreams summary at the top of the section:

[upstreams](#upstreams): where inference goes, whether Anthropic, Claude Platform on AWS, Bedrock, Agent Platform, or Foundry

B. Update the failover description

Before:

The gateway tries upstreams in order. 5xx, 429, timeouts, and missing-endpoint (501) fail over; other 4xx doesn't. 429 is per-upstream capacity, so provisioned-throughput (PT) exhaustion fails over to on-demand. An upstream that can't resolve the requested model is skipped without a network round-trip.

After:

The gateway tries upstreams in order. 5xx, 429, timeouts, missing-endpoint (501), and model-not-found responses fail over to the next upstream; other 4xx doesn't. 429 is per-upstream capacity, so provisioned-throughput (PT) exhaustion fails over to on-demand. An upstream that cannot be mapped for the requested model before a request is sent is still skipped without a network round-trip.

Impact

High - Prevents users from using a feature

Additional Context

Related v2.1.198 changes:

Gateway: added Claude Platform on AWS (anthropicAws) as an upstream provider; model-not-found responses now advance the failover chain

The quickstart page and the side-by-side gateway comparison table list the upstreams the gateway supports; these pages will need the same anthropicAws update so the new provider appears consistently across the gateway docs.

Affected Pages:

| Page | Context |
|---|---|
| https://code.claude.com/docs/en/claude-apps-gateway-config | Missing anthropicAws provider reference and model-not-found failover description |
| https://code.claude.com/docs/en/claude-apps-gateway | Provider comparison table and quickstart |

View original on GitHub ↗