Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

Fast-path AWS SSO credential resolution for profile-based auth

AWS SSO profile logins resolve faster via a direct fast path, falling back if anything unusual is configured.

You'll notice Notable No documentation found Improvements
JSON All of v2.1.221
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.221,
What probably matters to youSection of the release
What

With AWS_CONFIG_FILE set, credentials are resolved by reading the shared config and credentials files directly instead of going through the general ini provider, which cuts out a slower resolution path for plain SSO profiles.

Details
  • Requires sso_account_id and sso_role_name, and bails out if any other credential mechanism is configured: static keys, credential_process, role_arn, source_profile, credential_source, web_identity_token_file.
  • Reads the SSO token cache keyed by a sha1 of the session or start URL and validates expiry with a small zod schema.
  • Calls GetRoleCredentials against a region-pinned portal.sso host, with the result cached.
  • Any failure falls back to the previous fromIni path.
Evidence

host-pinned SSO leg failed

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleAWS_CONFIG_FILEsso_account_idsso_role_name

See this entry in the whole of v2.1.221 →

Feedback