Support passing credentials to Dyno as an alternative to passing Access Keys directly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
We should add support for a `credentials` option in the Dyno constructor options so that instead of having to specify the actual AWS Access Key and Secret Key (if you don't want to use the defaults), you can use any of the various Credential Providers/subclasses (see [here](http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Credentials.html)). This allows you to do useful things like use [TemporaryCredentials](http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/TemporaryCredentials.html) from an assumed role that will automatically refresh as needed.
This issue actually blocks implementation of [Kine #42](https://github.com/mapbox/kine/issues/42)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Dyno constructor options and review the AWS SDK Credentials and TemporaryCredentials documentation linked in the issue. Add support for a credentials option that accepts credential providers, then verify that temporary credentials from an assumed role can refresh as needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100