-
Notifications
You must be signed in to change notification settings - Fork 467
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
STSAssumeRoleSessionCredentialsProvider with external ID #367
Comments
I found the answer to Q2 by my self. |
I managed to get my requirement working by adding this class
And then properties |
If AWSCredentialsProviderPropertyValueDecoder had some mechanism to use the Builder pattern rather than string constructors then we would not need to write custom java code. |
Thanks for reporting this. We are currently working on the MultiLang Daemon for the 2.x release, and will be looking at making credentials creation easier. |
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
…r and construction. + added support for external ids (issue awslabs#367) + added support for endpoint+region (e.g., STS via VPC)
#1184) * [#367] Enhanced multi-lang `AWSCredentialsProvider=...` decoder and construction. + added support for external ids (issue #367) + added support for endpoint+region (e.g., STS via VPC) * Multiple multi-lang edits to introduce logging and additional tests. + added `ENDPOINT_REGION` nested key for a simpler Cx experience + deduplicated, and improved, logic w.r.t. CredentialsProvider construction to NOT swallow Exceptions * Relocated `multilang.properties` from `main/resources` to `test/resources`
(Please disregard the unintentional spam from force-pushing.) Starting w/ KCL 2.5.2, you no longer need to author your own Java class(es) to set an external id. This can now be done by appending an optional nested property of |
I am successfully using:
AWSCredentialsProvider = STSAssumeRoleSessionCredentialsProvider|arn:aws:iam::<account_id>:role/<role_name>|<session_name>
However I am now required to add an external id for the assume role.
STSAssumeRoleSessionCredentialsProvider
does support this but there does not seem to be a way to pass it in via theAWSCredentialsProviderPropertyValueDecoder
.I am not a java expert so it may be that it is not obvious exactly how to do that.
Question 2:
If I must write my own custom provider to get this functionality, must I also use the com.amazonaws.auth. namespace in order for AWSCredentialsProviderPropertyValueDecoder to find it?
The text was updated successfully, but these errors were encountered: