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.

Sign up for GitHub

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

Jump to bottom

Figure out where to store credentials #5

Open
gene1wood opened this issue Oct 31, 2017 · 2 comments
Open

Figure out where to store credentials #5

gene1wood opened this issue Oct 31, 2017 · 2 comments
Labels
Priority: Low Type: Enhancement

Comments

@gene1wood
Copy link
Owner

Storing them currently in config.yaml has these problems

  • hard to have stage and prod
  • risky as one could commit the file accidentally
  • must be stored mode 0600 then changed to 0644 to be added to the zip, then changed back to 0600
  • is located alongside the immutable code

We can't really use credstash as it uses KMS which isn't free
@gene1wood
Copy link
Owner Author

And now we're storing IAM user api keys in config.yaml even though it's not needed and shouldn't be accessible to the lambda function, as we share a single config for deploy.py and the lambda function =(

@gene1wood
Copy link
Owner Author

Should we use Parameter Store?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gene1wood