-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Comments
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. |
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. |
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. |
This issue has been fixed |
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?The text was updated successfully, but these errors were encountered: