Skip to content

Conversation

@stobrien89
Copy link
Member

@stobrien89 stobrien89 commented Oct 27, 2025

Issue #, if available:
Fixes #3197

Description of changes:
Adds support for resolving the region for STS clients created by assume role providers. By default, the credentials chain will pass client configuration to expose the top-level client's region. When providers are called outside the context of a client, they will accept region in-code configuration, region source profile configuration (for roles assumed via profiles), and will attempt to resolve AWS_REGION if any of the aforementioned options don't produce a region.

This also adds a notice that prompts to configure a region if a region cannot be found. These providers will still fall back to us-east-1, but this is likely to change in the future.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@stobrien89
Copy link
Member Author

Going a different direction with this. I'll let you know when it's updated

@stobrien89 stobrien89 force-pushed the bugfix-sts-providers branch from 3ce653f to 180280f Compare October 27, 2025 23:23
@stobrien89 stobrien89 force-pushed the bugfix-sts-providers branch from 180280f to 368f4cd Compare October 28, 2025 00:15
@stobrien89 stobrien89 force-pushed the bugfix-sts-providers branch from 368f4cd to cc4cb1d Compare October 28, 2025 00:32
@stobrien89 stobrien89 merged commit d055881 into aws:master Oct 28, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AssumeRoleWithWebIdentityCredentialProvider defaults to STS regional endpoint in us-east-1

2 participants