Add support to use regional endpoints for STS client while using assume role #10289
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jackye1995 @amogh-jahagirdar @nastra Please review. |
munendrasn
force-pushed
the
sts-regional-endpoint
branch
from
a1b7230
to
0e6f51a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
STS by default uses Global endpoint but AWS recommends to use regional endpoints.
The PR introduces new property
client.assume-role.sts-regional-endpoint-enabled, when set, stsClient is built region specified, else uses the global endpoint - default behaviourKeeping the current behaviour as the default, because for some regions regional point need to explicitly enabled. Once the user enables the regional endpoint, then the flag can be set