A few suggestions: 1. Application / service to service secrets should be handled either by Vault or AWS Param Store. Both are good. AWS Param Store is easier but less feature rich. Ideally, your Vault instance would have the database engine which allows for automatic rotation and password management of databases like Postgres. 2. Developers should only have access to AWS through SSO using something like Okta. Okta ha…
Ask HN: Secure and simple way for secret/credential management in a startup?
31–34 of 34 posts
Re: Ask HN: Secure and simple way for secret/credential management in a startup?
#32Earlier quoted context omitted.
Warning to anyone interested in Vault. Vault policies involve a learning curve. Maybe they have improved documentation and examples since I learned Vault management but I remember how complicated and time consuming it was.
For a small team I wouldn't go there. Except if the product requires a higher level of security and we have no money to spend on the SaaS or self-hosting is a requirement.
Re: Ask HN: Secure and simple way for secret/credential management in a startup?
#33Earlier quoted context omitted.
For a small team I wouldn't go there. Except if the product requires a higher level of security and we have no money to spend on the SaaS or self-hosting is a requirement.
The problem isn't self-hosting. It's the ongoing setup and management through their DSL.
Mentioning since I've def seen people get stuck and forget to consider the obvious.