4 ms·
So don’t provide secrets to your service via environment variable, it can leak? Instead, expose all your secrets via a public API with IP filtering, then give
by jakewins 2y ago
So don’t provide secrets to your service via environment variable, it can leak?
Instead, expose all your secrets via a public API with IP filtering, then give the credentials to this service to your app - as an environment variable - and voila!
This just seems like increasing complexity in a part of your system that should be as simple and non-dynamic as humanly possible, for the upside of.. much larger attack surface?
We inject secrets, as env vars, in each Deployment. No runtime access to any secrets store, gives the ability to generate new secrets for each deployment, and minimal complexity for such a critical aspect of the system.
- hinkley 2y agoOur (very) old system used enciphered secrets and an init script that got the key into a file and then unset the environment variable before the app started. But we never had a good system for sandboxes, which meant another way the local and deployment differed. They moved to a secret store instead. I don’t know if that’s better.