{"version":"2.1.321","anchor":"cloud-credential-env-vars-added-to-three-provider-env-allowl","canonical_anchor":"cloud-credential-env-vars-added-to-three-provider-env-allowl","heading":"AWS and Google credential variables added to cloud provider settings lists","tier":"internal","area":"Cloud Providers","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/cloud-credential-env-vars-added-to-three-provider-env-allowl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### AWS and Google credential variables added to cloud provider settings lists\n\nFive AWS and Google credential environment variables were added to three lists of cloud provider settings\n\n**Unclear.** What the three lists control, for example limits in managed settings or removal before running other programs, is not clear.\n\n**What**\n\nClaude Code keeps three lists of environment variables it treats as cloud provider settings. These variables were added to all three:\n\n- `AWS_SHARED_CREDENTIALS_FILE`\n\n- `GOOGLE_APPLICATION_CREDENTIALS`\n\n- `AWS_ACCESS_KEY_ID`\n\n- `AWS_SECRET_ACCESS_KEY`\n\n- `AWS_SESSION_TOKEN`\n\n`AWS_CONFIG_FILE` was also added to two of them. The lists already held variables such as `ANTHROPIC_BEDROCK_REGION_PREFIX`.\n\n**Why**\n\nThis changes how these credentials are handled for people using Amazon Bedrock or Google Vertex AI, including when they are set through settings files.\n\n- Area: Cloud Providers\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}