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

External secret store #71

Closed
robert-cronin opened this issue Aug 11, 2020 · 1 comment
Closed

External secret store #71

robert-cronin opened this issue Aug 11, 2020 · 1 comment
Assignees
Labels
development Standard development

Comments

@robert-cronin
Copy link
Contributor

There are some other external secret stores that sometimes users have to utilize.

For example to use AWS ECS and to put in secret keys in during deployment we use environment variables. However sometimes these keys should not be exposed to the infrastructure team.

So AWS allows one to get secret variables as paths to the AWS SSM.

So if a user were to be using AWS ECS/SSM then where does polykey fit into that picture?

There needs to be external push/pull integrations.

The HTTP interface is basically a pull integration that any external system can arbitrarily fetch.

But in some cases external push is needed. And this is currently facilitated through the other integrations already mentioned. Users have to be able to "put" stuff into SSM. And sometimes that could mean a manual clipboard copy & paste.

This is not an implementation task, this is just something for us to be wary of during our UI/UX design.

@robert-cronin
Copy link
Contributor Author

Closing on account of migration to gitlab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development
Development

No branches or pull requests

1 participant