We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like AssumeRoleCredentialsProvider assumes the credentials are coming from the environment, and there is no way to pass them explicitly.
AssumeRoleCredentialsProvider
The entry point is here, which decides whether to use credentials OR role.
aws4-axios/src/interceptor.ts
Lines 69 to 76 in 9066b38
But I think it is a valid use case to provide credentials, which will be used for STS.
Docs: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/STS.html#constructor-property
The text was updated successfully, but these errors were encountered:
Encounter the same issue when integrate multiple AWS profiles. @moltar did you found any workaround?
Sorry, something went wrong.
@jamesmbourne any thoughts?
You could write your own CredentialsProvider based on AssumeRoleCredentialsProvider.
CredentialsProvider
No branches or pull requests
It looks like
AssumeRoleCredentialsProvider
assumes the credentials are coming from the environment, and there is no way to pass them explicitly.The entry point is here, which decides whether to use credentials OR role.
aws4-axios/src/interceptor.ts
Lines 69 to 76 in 9066b38
But I think it is a valid use case to provide credentials, which will be used for STS.
Docs: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/STS.html#constructor-property
The text was updated successfully, but these errors were encountered: