-
Notifications
You must be signed in to change notification settings - Fork 215
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
ClientFactory to support regional STS Endpoints #289
Comments
Where are you picking up calls to the global endpoint? I don't see any calls to sts in client_factory.py and the only place I find sts is called in taskcat seems to already specify a region for the client. |
That may or may not work, but the documentation states the following: AWS STS recommends that you use both the setRegion and setEndpoint methods to make calls to a Regional endpoint. You can use the setRegion method alone for manually enabled Regions, such as Asia Pacific (Hong Kong). In this case, the calls are directed to the STS Regional endpoint. To learn how to manually enable a Region, see Managing AWS Regions in the AWS General Reference. If you use the setRegion method alone for Regions enabled by default, the calls are directed to the global endpoint of https://sts.amazonaws.com. |
Just tested it as well, you do need the endpoint. See snippet below.
|
Thanks for the research @vsnyc. Let's look at patching for now, even though, imho, intricacies like this should be handled in boto3/botocore |
we'll need to discover the endpoint url (seeing as it differs for some partitions) and sadly there doesn't seem to be a direct public method for this boto/boto3#1166 |
UPDATE: previos versions of this returned the global endpoint for sts. quick attempt at a generic endpoint finder function:
|
@jaymccon - Thanks. I'll be working on the PR within the coming days. That helps get me off the ground. |
This issue is now slated for the v0.9 branch. |
Adding regional endpoint support for STS clients. Closes #289
STS is now a regional-endpoint based services. Our calls to STS clients should reference a specific region rather than rely on the global endpoint.
The text was updated successfully, but these errors were encountered: