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

Prefer regional endpoint over global endpoint #1939

Closed
jpbarto opened this issue Apr 19, 2019 · 4 comments
Closed

Prefer regional endpoint over global endpoint #1939

jpbarto opened this issue Apr 19, 2019 · 4 comments
Labels
closed-for-staleness feature-request This issue requests a feature.

Comments

@jpbarto
Copy link

jpbarto commented Apr 19, 2019

Using a higher level AWS SDK which is underpinned by Boto3 I need to specify that the 'sts' client use the regional endpoint rather than the global endpoint. I don't see an easy way to set a preference for the regional endpoint over the global endpoint and I cannot use the endpoint_url argument as the SDK is instantiating the client, not me. Do I have any Pythonic options?

@joguSD
Copy link
Contributor

joguSD commented Apr 19, 2019

We don't have a configuration to use the regional endpoint over the global one. A configuration for this is something we've been considering adding so I'll mark this down as a feature request.

@joguSD joguSD added the feature-request This issue requests a feature. label Apr 19, 2019
@jpbarto
Copy link
Author

jpbarto commented Apr 21, 2019

Thank you. My specific use case has STS connectivity via an interface VPC endpoint. The Sagemaker Sdk makes a call to "session.client('sts')" which is incompatible with the regional endpoint. Currently I'm overwriting the client function of the Boto3 session with an interceptor function. Perhaps a client creation event could be used to attach a handler? I didn't see a suitable event in Boto3.

@github-actions
Copy link

Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. Because it has been longer than one year since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Aug 21, 2020
@swetashre
Copy link
Contributor

@swetashre swetashre added closing-soon This issue will automatically close in 4 days unless further comments are made. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Aug 21, 2020
@github-actions github-actions bot added closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-for-staleness feature-request This issue requests a feature.
Projects
None yet
Development

No branches or pull requests

3 participants