In my recent company, we use AWS Secrets Manager for all the applications where we store app-based, app-level secrets. We store all our secrets there. Currently, I'm working with AWS Secrets Manager and all encryption resources. In my company, we are using these secrets for the backend GoLang application. With the help of secrets stored in AWS Secrets Manager, the application fetches the secrets and works accordingly. AWS Secrets Manager is similar to a vault in our homes where we store important things. We encrypt those items and store them in AWS Secrets Manager so we don't have to carry them around or keep them somewhere unsafe. All the secrets are encrypted and stored in AWS Secrets Manager. The functionality involves taking the secrets and decrypting them, or if not encrypted, using them as they are. For all applications and resources such as database, MongoDB, Postgres, and everything which needs a username and password, it will be in AWS Secrets Manager. The code is structured to fetch from AWS Secrets Manager so it should not look anywhere else. It's the only place where we keep those important items.
The main benefit of using AWS Secrets Manager ( /products/aws-secrets-manager-reviews ) is that our applications retrieve the secrets dynamically at runtime. It allows us to configure the automatic rotational lambda function, which is essential for our current needs.
Find out what your peers are saying about Amazon Web Services (AWS), Microsoft, HashiCorp and others in Enterprise Password Managers. Updated: July 2025.
Enterprise Password Managers offer secure solutions for handling complex multi-user password requirements. They provide centralized management of credentials, enabling organizations to enhance security and compliance.By using Enterprise Password Managers, organizations can efficiently streamline password management processes, ensuring robust protection against unauthorized access. Features like audit trails, user activity monitoring, and seamless integration with existing IT infrastructures...
In my recent company, we use AWS Secrets Manager for all the applications where we store app-based, app-level secrets. We store all our secrets there. Currently, I'm working with AWS Secrets Manager and all encryption resources. In my company, we are using these secrets for the backend GoLang application. With the help of secrets stored in AWS Secrets Manager, the application fetches the secrets and works accordingly. AWS Secrets Manager is similar to a vault in our homes where we store important things. We encrypt those items and store them in AWS Secrets Manager so we don't have to carry them around or keep them somewhere unsafe. All the secrets are encrypted and stored in AWS Secrets Manager. The functionality involves taking the secrets and decrypting them, or if not encrypted, using them as they are. For all applications and resources such as database, MongoDB, Postgres, and everything which needs a username and password, it will be in AWS Secrets Manager. The code is structured to fetch from AWS Secrets Manager so it should not look anywhere else. It's the only place where we keep those important items.
The main benefit of using AWS Secrets Manager ( /products/aws-secrets-manager-reviews ) is that our applications retrieve the secrets dynamically at runtime. It allows us to configure the automatic rotational lambda function, which is essential for our current needs.
We store all our sensitive data in Secrets Manager.
I use AWS Secrets Manager to securely store and manage sensitive information with automatic encryption.
AWS Secrets Manager takes care of managing the secret within AWS and other AWS services.
We use AWS Secrets Manager to store secrets for the EKS cluster for our microservice infrastructure.
We use the solution to host secret credentials. It helps us orchestrate our platform and the customer's environment.
In our office, we have experiments that require handling card details and card data, which is why I am exploring ways to protect them.
The primary use case of the solution is to manage credentials and access.
It is primarily being used by our application for most of its application secrets.
Using this product, we allow our users to store certain secrets. It will store them and allow users to access them when they want.