{"version":"2.1.239","anchor":"aws-and-google-endpoint-variables-handled-explicitly","canonical_anchor":"aws-and-google-endpoint-variables-handled-explicitly","heading":"AWS and Google endpoint variables handled explicitly","tier":"notice","area":"Bedrock","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/aws-and-google-endpoint-variables-handled-explicitly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### AWS and Google endpoint variables handled explicitly\n\nAWS and Google custom endpoint variables are now forwarded and scrubbed deliberately.\n\n**What**\n\nCloud endpoint overrides are now in the list of environment variables Claude Code forwards and scrubs deliberately, so Bedrock and Vertex users pointing at custom endpoints get consistent treatment.\n\n**Details**\n\n- Added: `AWS_ENDPOINT_URL`, `AWS_ENDPOINT_URL_STS`, `AWS_ENDPOINT_URL_BEDROCK`, `AWS_ENDPOINT_URL_BEDROCK_RUNTIME` and the SSO\/OIDC variants, plus `CLOUDSDK_CONFIG`, `GCLOUD_PROJECT` and `GOOGLE_EXTERNAL_ACCOUNT_ALLOW_EXECUTABLES`.\n- A separate environment-scrubbing helper drops its agent-proxy and settings-color special cases and gains an additional set of variables it deletes.\n\n**Evidence**\n\n`AWS_ENDPOINT_URL_BEDROCK_RUNTIME`\n\n- Area: Bedrock\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}