Announcement: Upcoming credential resolution change #1972
sichanyoo
announced in
Announcements
Replies: 3 comments
-
The release date for the above change has been changed to 7/15/25 due to unexpected change in release schedule. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This is delayed again for now, this post will be updated once date gets finalized. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This change was released today (7/16/25) with v1.5.0: https://github.com/awslabs/aws-sdk-swift/releases/tag/1.5.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Announcement
On 7/16/2025, Wednesday, AWS SDK for Swift will change its credential resolution order in the
ProfileAWSCredentialIdentityResolver
chain and theDefaultChainAWSCredentialIdentityResolver
. The changes outlined below will be released with a minor version bump. If your environment has credentials configured in multiple ways, changes described below may cause your application to start to resolve credentials from different places than before.Please see below for more details:
ProfileAWSCredentialIdentityResolver change
The order of sources looked at for credentials in
ProfileAWSCredentialIdentityResolver
will change as outlined below:Currently:
Will be changed to:
DefaultAWSCredentialIdentityResolver change
The order of sources looked at for credentials in
DefaultAWSCredentialIdentityResolver
will change as outlined below:Currently:
a. Profile: assume role with source profile
b. Profile: assume role with named provider / credential_source
c. Profile: process
d. Profile: shared credentials file
a. Environment variables: web identity token / STS
b. Profile: web identity token / STS
Not part of default chain:
Will be changed to:
a. Profile: shared credentials file
b. Profile: assume role with source profile
c. Profile: assume role with named provider / credential_source
d. Profile: web identity token / STS
e. Profile: SSO role credentials
f. Profile: legacy SSO
g. Profile: process
Reason this change
Having a standard credential resolution order among SDKs & AWS CLI is very important because it allows seamless transition between the tools where credentials continue to get resolved from the same place regardless of the tool used. This change allows AWS SDK for Swift to be in sync with the current cross-SDK standard for credential resolution.
Beta Was this translation helpful? Give feedback.
All reactions