AWS Secrets Manager - The Default Choice
Use Cases and Deployment Scope
<div>We have most of our infra on AWS, so naturally, AWS Secrets Manager plays a key role in managing the secrets.</div><div>
</div><div>Be it DB connection string, url, username, password, etc. all the little pieces that allow a service to connect to other services to do meaningful things, we store everything in AWS Secrets Manager.</div>
Pros
- Single source of truth for secrets
- Securely share secrets with colleagues
- Securely store secrets for services to access during runtime
Cons
- The whole secret vs key-value naming could be confusing for beginner
- The lack of history is quite inconvenient
Likelihood to Recommend
<div>If you need a secret manager, where you can store key-value pairs of secrets for the whole team & the services to retrieve then AWS Secrets Manager is a good choice, especially when your infra is already on AWS.</div><div>
</div><div>With a proper setup, AWS Secrets Manager can be seamlessly integrated into your infra.
</div>