{"version":"2.1.321","anchor":"gateway-warning-for-base-url-env-vars-changed-and-now-covers","canonical_anchor":"gateway-warning-for-base-url-env-vars-changed-and-now-covers","heading":"Without base_url, cloud provider requests go to the default endpoint, not the env var","tier":"notice","area":"Gateways","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/gateway-warning-for-base-url-env-vars-changed-and-now-covers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Without base_url, cloud provider requests go to the default endpoint, not the env var\n\nThe gateway no longer reads the Bedrock, Vertex or Foundry base-URL variables, and Bedrock without `base_url` uses its regional endpoint\n\n**What**\n\nClaude Code can reach models through Amazon Bedrock, Google Vertex and Microsoft Foundry. A base URL is the address requests are sent to.\n\n- The gateway's warning about base-URL environment variables now also covers `ANTHROPIC_FOUNDRY_BASE_URL`, as well as the Bedrock and Vertex ones.\n\n- The warning now says the gateway does not read the variable. Requests for upstreams with no `base_url` go to the provider's default endpoint. To keep a custom address, copy the URL into `base_url`. Before, the warning said such requests went to that URL whatever the upstream's region.\n\n- Bedrock always gets an explicit address. With no `base_url`, it uses `https:\/\/bedrock-runtime.${region}.amazonaws.com` built from the profile's region.\n\n**Why**\n\nIf you relied on these environment variables to send requests to a custom address, such as a private endpoint, set `base_url` instead or requests will go to the provider's default.\n\n- Area: Gateways\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}