paint-brush
AWS Secrets Manager vs. Hashicorp Vault vs. AWS Parameter Storeby@nimboya
15,884 reads
15,884 reads

AWS Secrets Manager vs. Hashicorp Vault vs. AWS Parameter Store

by Ewere Diagboya3mMay 22nd, 2018
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

As you move faster and faster with your DevOps practice, there is a piece of the puzzle that seems to be a little snag. That snag can cost you a whole lot, in terms of system security, management and updates. Application Parameters/Configurations; these guys practically determine how our applications run. It spans across database connection, to login credentials for RabbitMQ and other secret credentials. As a security practice, you do not want these credentials to be visible in your codebase when committing your code to your VCS (Version Control System). One of the ways to secure these credentials is by using Environment Variables which can be injected in the particular environment you need those secrets and configurations, instead of the values as they are. There also needs to be a place where these data need to be stored for safe keeping and if possible encrypted where they are stored.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - AWS Secrets Manager vs. Hashicorp Vault vs. AWS Parameter Store
Ewere Diagboya HackerNoon profile picture
Ewere Diagboya

Ewere Diagboya

@nimboya

L O A D I N G
. . . comments & more!

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite