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

Support for AWS_STS_REGIONAL_ENDPOINTS #964

Open
BharatKJain opened this issue Oct 30, 2023 · 1 comment
Open

Support for AWS_STS_REGIONAL_ENDPOINTS #964

BharatKJain opened this issue Oct 30, 2023 · 1 comment

Comments

@BharatKJain
Copy link

When the env AWS_STS_REGIONAL_ENDPOINTS is set to regional, it's calling sts.amazonaws.com whereas it should call sts.ap-south-1.amazonaws.com or some other regional endpoint.

AWS docs reference

This helps when we're haskell code running in a closed environment where there's no internet available to make the STS calls, and regional endpoints can be used using VPC endpoints service which allows direct connectivity to some services.

@BharatKJain
Copy link
Author

More information on this issue, python is handling each region's endpoint in a botocore file present in this relative path: botocore/data/endpoints.json

Should we handle it like this? Or some other way?

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

No branches or pull requests

1 participant