Failed to load assume role, of profile, failed to get shared config profile

[skmcgrail]

The SDK appears to have a bug that does not exist in the V1 SDK. Given the following config and credentials setup the SDK will return an unexpected error failed to load assume role foofoofoofoofoofoofoofoofoofoofoofoofoofoo, of profile A, failed to get shared config profile, A.

~/.aws/config:

[default]
region=us-west-2
external_id=FooBar
role_session_name=FooSessionName
role_arn=foofoofoofoofoofoofoofoofoofoofoofoofoofoo
duration_seconds = 43200
source_profile=A

[profile A]
external_id=AExternalID
role_session_name=ASessionName
role_arn=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
duration_seconds = 43210
source_profile=B

~/.aws/credentials:

[A]
aws_access_key_id=A_PROFILE_ACCESS_KEY_ID
aws_secret_access_key=A_PROFILE_SECRET_ACCESS_KEY
aws_session_token=A_PROFILE_SESSION_TOKEN

[B]
aws_access_key_id=B_PROFILE_ACCESS_KEY_ID
aws_secret_access_key=B_PROFILE_SECRET_ACCESS_KEY
aws_session_token=B_PROFILE_SESSION_TOKEN

[skmcgrail]

Root cause is due to the V2 SDK incorrectly normalizing profile names, which should be treated as case-sensitive. Thus when attempting to lookup profile A, this would fail due to the normalization that had occurred during the INI parsing. This bug in behavior will be fixed in an upcoming release.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.