This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
Enable use of AWS STS regional endpoints #348
Merged
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
|
@Aneurysm9 can you rebase or recreate this PR so CI is run, there was an issue with the GH actions workflow not triggering on PRs :) |
…ts into regional_sts
Flydiverny
approved these changes
Apr 26, 2020
This was referenced Jan 16, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The default STS configuration uses the legacy global endpoint, which does not work from private VPCs accessing STS via VPC Endpoints. This change adds the
regionandstsRegionalEndpointsvalues to thestsConfigobject used to construct the STS client. It defaults to "regional" as the value ofstsRegionalEndpointsbut honors theAWS_STS_ENDPOINT_TYPEenvironment variable for users who prefer/require the use of "legacy" endpoints.