3 ms·
We've been using EnvKey since nearly the first day it was launched, and it has really made key management for our project and team easier on a massive scale. P
by cyberferret 9y ago
We've been using EnvKey since nearly the first day it was launched, and it has really made key management for our project and team easier on a massive scale.
Prior to that, we were looking at Vault or the AWS baked in key management solutions, but all of those were extremely tedious to set up and maintain. In total honesty, we migrated over to EnvKey within about 20 minutes (from over 30 secrets stored in server environment variables and .env files. Adding new secrets for new services takes a few seconds, and there is no need for us to redeploy elastic beanstalk instances when we do. EnvKey is definitely one of the 'top five' third party services that we integrated with for our development work, and we are still on the grandfathered free plan, and received no incentives for posting this, other than being a grateful customer.
- sametmax 9y agoSo when EnvKey fails or is under attack, you lost access (or give away MITM) to all your infra ?
- ipfaffy 9y agoThis is the key to me. This tech would make life easier, but what happens when there is an outage or they get hacked or $reason?
- topraman 9y agothis
- danenania 9y agoThis is of course a legitimate concern, but it's also one that is addressed in EnvKey's design. Client-side encryption means that even if we are attacked, no sensitive data will be exposed. And we have a failover to S3 so that you won't lose access if the service goes down. Storing config and secrets obviously requires trust, but at the same time, many other services that developers use without a second thought actually require a lot more trust than EnvKey does.