Skip to content
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

Adding Environment Variable Credential Support #13

Merged
merged 3 commits into from
Feb 28, 2020

Conversation

jshodd
Copy link
Contributor

@jshodd jshodd commented Feb 26, 2020

This pull request resolves issue #12 by allowing the user to utilize AWS credentials in environment variables. this is done by injecting the following environment variables into the container when executing commands:

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_SESSION_TOKEN
  • AWS_SECURITY_TOKEN

This will allow users to utilize tools such as https://github.com/segmentio/aws-okta to run the application. In order to use this functionality instead of using a profile, I have added the --env flag to load credentials via environment variable instead of aws profile. When the --env flag is used and a database is not specified, I have it default to general.db for lack of a better name.

I have tested this on several of our accounts with success. If you have any suggested changes please let me know!

Co-Authored-By: beatro0t <[email protected]>
@jshodd jshodd requested a review from beatro0t February 27, 2020 17:45
@beatro0t beatro0t merged commit 08a3f88 into WithSecureLabs:develop Feb 28, 2020
@beatro0t beatro0t linked an issue Feb 28, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow credentials to be passed by environment variables.
2 participants