-
Notifications
You must be signed in to change notification settings - Fork 186
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 authentication on global region for AWS IAM (close #758) #763
Conversation
@Amuerte Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@Amuerte Thank you for signing the Contributor License Agreement! |
Close #758 |
7585758
to
7e14733
Compare
7e14733
to
d78dd13
Compare
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.
I'm not quite sure this pull request makes sense as all we do is setting a Region
/** | ||
* Build a new {@link AwsIamAuthenticationOptions} instance. | ||
* @return a new {@link AwsIamAuthenticationOptions}. | ||
*/ | ||
public AwsIamAuthenticationOptions build() { | ||
|
||
Assert.state(this.credentialsProvider != null, "Credentials or CredentialProvider must not be null"); | ||
if (useGlobalEndpoint) { |
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.
If using the global endpoint is merely a matter of providing the right Region
, why don't you just call regionProvider(() -> Region.US_EAST_1)
?
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.
mmh good point you raised here 😅 . By looking more in details, we are blocked because we are using spring-cloud-vault-config to instantiate the AwsIamAuthentication
, and it does not offer a way to configure the region.
I will create an issue and a PR there. Sorry for that.
This PR enables one to perform AWS IAM authentication when the Vault instance is configured on the Global STS endpoint (us-east-1) and the application is deployed on another region.