Skip to content

Take into account the AWS_STS_REGIONAL_ENDPOINTS#1227

Merged
fviard merged 1 commit intos3tools:masterfrom
lanzrein:patch-sts-regional-endpoints
Jan 21, 2022
Merged

Take into account the AWS_STS_REGIONAL_ENDPOINTS#1227
fviard merged 1 commit intos3tools:masterfrom
lanzrein:patch-sts-regional-endpoints

Conversation

@lanzrein
Copy link
Copy Markdown

This fixes the issue where the sts endpoint sts.amazonaws.com is not
accessible.
Take into account the environment varialbe AWS_STS_REGIONAL_ENDPOINTS
If the AWS_STS_REGIONAL_ENDPOINTS variable is provided check for AWS_REGION env var to decide
region.

If AWS_REGION is not provided use the same region as the bucket.
(bucket_location parameter)

@aperigault
Copy link
Copy Markdown

Hi,
tested here and it solved my problem.

Thanks !

@fviard
Copy link
Copy Markdown
Contributor

fviard commented Jan 19, 2022

It's all good now, thank you.

Could you "squash" your changes into a single commit before I merge please?

This fixes the issue where the sts endpoint sts.amazonaws.com is not
accessible.
Take into account the environment varialbe AWS_STS_REGIONAL_ENDPOINTS
If the variable is provided check for AWS_REGION env var to decide
region.
IF AWS_REGION is not provided use the same region as the bucket.
(bucket_location parameter)
@lanzrein lanzrein force-pushed the patch-sts-regional-endpoints branch from 4eb52f5 to dbee02a Compare January 21, 2022 12:53
@lanzrein
Copy link
Copy Markdown
Author

Should be all good !

@fviard fviard merged commit 6927469 into s3tools:master Jan 21, 2022
@fviard
Copy link
Copy Markdown
Contributor

fviard commented Jan 21, 2022

Merged, thank you!

@aperigault
Copy link
Copy Markdown

Thank you @fviard. Can we have a release with this fix included please ?

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.

3 participants