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
AWS SDK already has a pattern for sourcing credentials https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-credentials-node.html
By explicitly forcing users to provide key and secret you break the other flows such as AWS_PROFILE
Work around is to use a thirdparty cli tool for generating temp creds before hand such as https://www.npmjs.com/package/aws-assume for legacy apps
Edit: Get a token invalid error using the above, had to monkey patch
The text was updated successfully, but these errors were encountered:
Once I'm up and running, will look at PR
Sorry, something went wrong.
Fixed in #182
No branches or pull requests
AWS SDK already has a pattern for sourcing credentials
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-credentials-node.html
By explicitly forcing users to provide key and secret you break the other flows such as AWS_PROFILE
Work around is to use a thirdparty cli tool for generating temp creds before hand such as https://www.npmjs.com/package/aws-assume for legacy apps
Edit: Get a token invalid error using the above, had to monkey patch
The text was updated successfully, but these errors were encountered: