Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUN-2824: rebuild #136

Merged
merged 2 commits into from
Oct 22, 2024
Merged

RUN-2824: rebuild #136

merged 2 commits into from
Oct 22, 2024

Conversation

gschueler
Copy link
Member

from #131

kangaechu and others added 2 commits September 3, 2024 16:55
This modification allows the use of STS regionalized endpoints by specifying the AWS_STS_REGIONAL_ENDPOINTS=regional environment variable.

AWS STS has global and per-region endpoints.
https://docs.aws.amazon.com/sdkref/latest/guide/feature-sts-regionalized-endpoints.html

AWS recommends STS regionalized endpoints (AWS_STS_REGIONAL_ENDPOINTS=regional), but defaults to STS global endpoints (AWS_STS_REGIONAL_ENDPOINTS=legacy ).

On August 29, 2024, an AWS STS failure occurred and requests using the STS global endpoints failed.
This failure did not affect requests using STS Regionalized endpoints.

The current implementation uses AWS SecurityTokenServiceClient when creating sts clients. This method is deprecated and does not read the STS endpoint configuration.

Instead, the AWSsecurityTokenServiceClientBuilder is used to allow the STS endpoint settings to be respected.
RUN-2824: Respect the AWS_STS_REGIONAL_ENDPOINTS parameter
@gschueler gschueler merged commit 8df6f6e into master Oct 22, 2024
1 check passed
@gschueler gschueler deleted the RUN-2824 branch October 22, 2024 19:49
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.

2 participants