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
[STS]Support opt-in regional STS endpoint #2090
Conversation
cc @jasdel & @howardlopez for review :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but should there be a test that verifies the sts_regional_endpoints
value is taken from the env source first over the config file?
Also, does this need a changelog?
@howardlopez Added tests and changelog ;) |
Hi! This PR breaks for us.
|
We are experiencing the same issue. |
Our error seems related to the Aws::CloudFront::Client
.new(credentials: credentials, region: 'us-east-1') It looks like CloudFront was updated with the latest release of aws-sdk-core:
During our application deployment. That results in the following stack trace:
|
From your log, looks like you are on an outdated partition gem version, mind update to https://rubygems.org/gems/aws-partitions/versions/1.228.0 and let me know whether it works? |
@cjyclaire Already testing it. |
@cjyclaire Testing it now. |
Thanks again for reporting! if confirming the new version has fixed the issue, I'll update core gemspec to make sure that version is a minimum requirement |
Sorry for the delay - we had to make a few other changes in addition to the fix for this one. We are good to go after upgrading that dependency. Thanks for the quick response, @cjyclaire! |
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
WIPThis PR support opt-in STS regional endpoints by setting
sts_regional_endpoints: 'regional'
at client or from ENVAWS_STS_REGIONAL_ENDPOINTS
orsts_regional_endpoints
in shared configBy default, SDK set
sts_regional_endpoints: 'legacy'
, previous non-regionalized regions will stay with global endpoints