{"version":"2.1.285","anchor":"bedrockaws-user-agent-and-credential-profile-keys","canonical_anchor":"bedrockaws-user-agent-and-credential-profile-keys","heading":"AWS client identifies itself as AnthropicAws\/JS and lists profile keys","tier":"internal","area":"Bedrock","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bedrockaws-user-agent-and-credential-profile-keys","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### AWS client identifies itself as AnthropicAws\/JS and lists profile keys\n\nRequests from the AWS client now carry the name AnthropicAws\/JS, and it keeps a list of AWS profile sign-in keys\n\n**Unclear.** How the list of profile setting names is used is not known.\n\n**What**\n\nThe client Claude Code uses to reach Anthropic models through AWS now sends a user agent of `AnthropicAws\/JS`. A user agent is the name a program attaches to each request to say what it is.\n\nIt also now holds a list of AWS profile setting names, including `sso_account_id`, `sso_role_name`, `sso_session`, `credential_process` and `web_identity_token_file`.\n\n**Why**\n\nIf you read AWS request logs, requests from Claude Code will show up under this name.\n\n- Area: Bedrock\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}