AWS Secrets Manager - The Default Choice
Updated October 22, 2024

AWS Secrets Manager - The Default Choice

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with AWS Secrets Manager

We have most of our infra on AWS, so naturally, AWS Secrets Manager plays a key role in managing the secrets.

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.

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
  • The ability to securely store & share secrets greatly improves security posture
  • Services can be made to retrieve secrets externally at runtime
  • Can control secrets for different environments for different groups of people
Both AWS Secrets Manager & MS Azure Key Vault are pretty similar. They're the default secrets manager on their respective cloud platform.

The choice comes down to where your infra resides on.

Do you think AWS Secrets Manager delivers good value for the price?

Yes

Are you happy with AWS Secrets Manager's feature set?

Yes

Did AWS Secrets Manager live up to sales and marketing promises?

Yes

Did implementation of AWS Secrets Manager go as expected?

Yes

Would you buy AWS Secrets Manager again?

Yes

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.

With a proper setup, AWS Secrets Manager can be seamlessly integrated into your infra.

Comments

More Reviews of AWS Secrets Manager

  1. Home
  2. Secret Managers
  3. AWS Secrets Manager Reviews
  4. User Review of AWS Secrets Manager