AWS SSO profile logins resolve faster via a direct fast path, falling back if anything unusual is configured.
What's wrong with this entry?
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.
- Requires
sso_account_idandsso_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.
host-pinned SSO leg failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.