AWS Secrets Manager Reviews

I use it for handling any confidential tasks or operations within my systems. 
Typically, we rely on the AWS Identity and Access Management center to set specific rules. In most cases, systems autonomously manage the secrets. While there are admins who can handle secrets from the console, we aim to minimize such instances.

AWS Secrets Manager has streamlined our processes for managing secrets and their lifecycle. We typically handle everything through automation, following a predefined approach. When we undertake our developments, we seamlessly integrate the process into our workflows. Essentially, our secrets require minimal intervention; they are automatically managed by the system itself. This ensures smooth operations without the need for manual intervention.

We integrate this tool with various AWS services, utilizing AWS Secrets Manager specifically for AWS resources. Any application, service, or deployment within AWS leverages Secrets Manager whenever it requires access to it.

I use AWS Secrets Manager to securely store and manage sensitive information with automatic encryption.

AWS Secrets Manager has improved my application's security by securely storing and automatically rotating sensitive information like passwords.

AWS Secrets Manager is used for storing secret information that has to be a secret from your customer and your employees. They would need your credentials. When you use a Google service for something, you have to log in using your credentials, even when you are accessing it programmatically. You cannot include these things in the program because programs are stored outside our community in some repository or version control system like GitHub. So you cannot add these credentials in the code because it is public. For that, we store it in AWS Secrets Manager, and whoever writes the program connects with the solution to fetch the authentication information. Even the person who writes the program doesn't need to know the guarded secret.

Even though I said that the employee or programmer doesn't need to see the secret, he can view the secret if he intends to. He just has to display the value he fetched from the AWS Secrets Manager.

The solution should add one more layer of encoding and decoding so that when the programmer fetches the value from the AWS Secrets Manager, what he receives is only an encoded version. Instead of directly sending it to Google, he sends the authentication information to another AWS service which decodes it and then sends it to Google. If you add one more layer of security to AWS Secrets Manager, even the programmer will not be able to see the secrets.

We use the solution to host secret credentials. It helps us orchestrate our platform and the customer's environment.

We can utilize the solution directly through the access feature in the certificate. Thus, we don't have to maintain or create another vault for ourselves. It brings more speed and flexibility to the development team.

AWS Secrets Manager takes care of managing the secret within AWS and other AWS services. 

With AWS Secrets Manager, we can configure the required secrets in the secret manager, and we can access that from the Lambda service without any additional effort.

So, we just have to update policies. Based on that policy, we automatically allow the Lambda service to access the response secret manager.

In our office, we have experiments that require handling card details and card data, which is why I am exploring ways to protect them.

It's for critical environments, servers, and overall protection are the most valuable feature.

We store all our sensitive data in Secrets Manager.

Secrets Manager helps in retrieving the enrollment variables used by the code. We also find AWS Glue useful for ETL processes along with AWS EMR for its Spark engine.

We are using AWS Secrets Manager for credentials that we need to use, such as system-to-system credentials. Additionally, we have user credentials in our IM solutions.

The most valuable feature of AWS Secrets Manager is the ability to keep data secret and assign access permissions to people to grant or restrict access.

They offer rotation configurations that enable you to create a Lambda function to rotate your secret on a scheduled basis, whether it's a certificate or any other type of credential.