AWS Secrets Manager vs. Microsoft Azure Key Vault

[AWS Secrets Manager] is really good at managing the secrets for each environment (stage, production, ...), and with a simple command, the users will get all the variables for running the project. Depending on the user role, they could just read and/or edit the variables on the Secrets Manager on AWS. This facilitates the management of the secrets.

Incentivized

You can back up many local keys in Microsoft Azure Key Vault, easy to set up permission. It helps your information protection task. Integration with local systems is also possible with some solutions. If you are using old systems, you may not get the full benefit of Microsoft Azure Key Vault. But I recommend to try it.

Incentivized

• Single source of truth for secrets
• Securely share secrets with colleagues
• Securely store secrets for services to access during runtime

Incentivized

• It could be good if a user can use a variable in the project but can't see them in the manager on AWS

Incentivized

It is easy to use. The cost of this service is quite low, so don't worry about it. It is very easy to use because you can store keys in a variety of ways. It would be very nice to have the ability to automatically remind the person in charge of the key expiration date.

Incentivized

How to use Microsoft Azure Key Vault is available in Micrsoft tech net or various internet tech sites. If you have a question, you can use support from pages in Azure. Onece you request, you will get call or e-mail from Microsoft. Public information referrals and service bugs will be handled free of charge

Incentivized

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.

Incentivized

• Costs are suitable
• ROI is positive

Incentivized