No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Secrets Manager vs Azure Key Vault comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 11, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Secrets Manager
Ranking in Enterprise Password Managers
3rd
Ranking in Secrets Management Tools
3rd
Average Rating
9.0
Reviews Sentiment
6.8
Number of Reviews
17
Ranking in other categories
No ranking in other categories
Azure Key Vault
Ranking in Enterprise Password Managers
1st
Ranking in Secrets Management Tools
2nd
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
52
Ranking in other categories
Certificate Management Software (1st), Microsoft Security Suite (20th)
 

Mindshare comparison

As of August 2026, in the Enterprise Password Managers category, the mindshare of AWS Secrets Manager is 13.9%, down from 17.2% compared to the previous year. The mindshare of Azure Key Vault is 14.9%, down from 19.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Password Managers Mindshare Distribution
ProductMindshare (%)
Azure Key Vault14.9%
AWS Secrets Manager13.9%
Other71.2%
Enterprise Password Managers
 

Q&A Highlights

NC
Content Manager at PeerSpot
Nov 24, 2021
 

Featured Reviews

Mahadev Metre - PeerSpot reviewer
Dev Ops Engineer at Paydoh
Consistent security and efficiency improvements optimize IT infrastructure with effective management
When creating AWS Secrets Manager, it should be automated using tools such as Terraform, Puppet, or Ansible. With Terraform code, you specify the encryption key, secret name, rotation policy, and secret replication. Human error occurs when feeding secret values manually, especially with large amounts of secrets to input. Secrets should never be protected only by IAM. They should be protected by multiple layers, such as IAM and one or two KMS keys. Additional security measures could be beneficial if necessary. The rotation policy is crucial because some secrets may become obsolete, require updates, or get compromised. With a weekly rotation policy, if unauthorized access occurs, the exposure is limited to seven days. The rotation policy can be customized according to needs.
Rajthilak BS - PeerSpot reviewer
Associate Vice President (Data Security & Protection - Confidential AI) at Standard Chartered Bank
Have addressed compliance challenges but still struggle with seamless integration of certificate issuance between environments
In terms of Azure Key Vault improvements, we have to compare the competitor. If we consider AWS, our bank has Microsoft PKI, which is a Microsoft product, for the entire digital certificate infrastructure. Even in the cloud, when it is AWS, the internal certificates are MS PKI. When we had a problem, users had to come to on-premise to get a certificate and import it to AWS Certificate Manager and assign it. We wondered why we could not issue the certificate directly from the cloud for cloud users. There was a simple way in AWS. They have a Private Certificate Authority (PCA) and Amazon Certificate Manager. Private Certificate Authority issues certificates to Amazon services. They also provide Amazon Certificate Manager to store and deploy certificates. These are two neat components - one is an issuer and another is storage and deployment solutions for certificates. With PCA, I can directly enable it and get certificates from AWS itself. AWS can issue SSL/TLS certificates if you enable it directly. If you consider Azure, it is not very clear. Even the naming convention, Key Vault, might not suggest that this is a PKI or certificate manager. You cannot issue certificates directly. They have app certificates and did not have a clear-cut certificate management solution in the cloud when I worked at that time. I am not sure whether they have updated Azure Key Vault as a full-fledged PKI solution now. From what I saw, it was not a full-fledged PKI solution. We are not majorly using Azure Key Vault because it is only for storing secrets. If some solutions can provide guidance on how we can maximize leverage, we can immediately look forward to doing that. We already have some business problems we want to solve. While our primary focus is AWS, many of the services such as ADO are running on Azure, and the secondary services are growing bigger.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is security."
"The API is fine and works well."
"The most valuable feature is the management of credentials."
"Secrets Manager helps in retrieving the enrollment variables used by the code."
"Integrating with other services was straightforward, especially within the AWS environment."
"In summary, this is a good product and well suits our needs."
"I would highly recommend AWS Secrets Manager for secret management in AWS."
"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."
"Overall, it's a great product."
"The product’s advantageous feature is integration."
"The most valuable feature of Azure Key Vault is the secret storage of data."
"With Azure Key Vault you have something that is free, enterprise-level, global, and it just works."
"This is a very user friendly solution and the security level is very high."
"The centralized storage and secure storage are features we like."
"In summary, this is a good product and one that I recommend."
"Azure Key Vault allows only identified users to get the credentials and rotates the keys automatically."
 

Cons

"We occasionally have problems with rate limits, although that is a problem more generally with AWS."
"The sidecar feature has room for improvement."
"AWS Secrets Manager could support hybrid infrastructure."
"If you don't have enterprise support, then you will not be able to get through to them to get the help. It is not only applicable to AWS Secrets Manager. It is also applicable to any service on AWS."
"The solution's initial setup process is complicated."
"We contacted AWS support and waited approximately an hour for assistance."
"There is a potential improvement in connecting AWS Secrets Manager to Jenkins CI/CD pipeline to automatically reflect changes in production."
"There is room for improvement in the pricing model."
"It needs to offer dynamic secrets management."
"I think the product needs upgrades in terms of access control and certification improvements."
"One area for improvement is the notification system for secret expiration. It would be beneficial if the service could handle this more autonomously, eliminating the need for additional integrations."
"Sometimes, we face issues that the support team is not aware of, necessitating investigation from their end."
"The solution needs to improve reliability and protection."
"The product must provide AI features."
"The solution's usage can be a little better from the user interface point of view."
"The voucher access policy can be improved by configuring it based on groups, rather than just applications or users."
 

Pricing and Cost Advice

"We've observed that AWS Secrets Manager pricing is based on a per-secret-per-month model. As a result, we prefer to divide our secrets into individual pieces to increase security and grant specific access permissions to certain secrets, systems, or individuals. However, this approach results in higher costs. Therefore, we have been exploring ways to combine our secrets into groups to reduce expenses and simplify management. Nonetheless, we acknowledge that this issue may not be related to the secret manager's functionality."
"The solution is expensive."
"We purchase a monthly license for the product."
"I don't believe there is a license cost for the solution."
"The cost is somewhat high."
"The pricing is decent. It has a pretty low price. It is a straightforward cost based on usage."
"You don't need to pay for a license for Azure Key Vault. It is billed on a pay-as-you-go basis."
"It is a cheap option."
"The product is affordable, in my opinion."
"Currently, the solution's pricing is based on the number of transactions, which is very high in some cases."
"Pricing is quite reasonable and support is included, although premium support is available for an additional fee."
"Currently, the tool's monthly licensing costs are around 1,800 USD for all the environments combined, including the production and pre-production environments."
"The product costs much less compared to other vendors."
report
Use our free recommendation engine to learn which Enterprise Password Managers solutions are best for your needs.
909,153 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
8%
Comms Service Provider
8%
Manufacturing Company
8%
Financial Services Firm
12%
Manufacturing Company
9%
Computer Software Company
8%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Large Enterprise10
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise11
Large Enterprise27
 

Questions from the Community

Which is better - Azure Key Vault or AWS Secrets Manager?
Azure Key Vault is a SaaS solution. You can easily store passwords and secrets securely and encrypt them. Azure Key Vault is a great solution to ensure you are compliant with security and governanc...
Which is better - HashiCorp Vault or AWS Secrets Manager?
HashiCorp Vault was designed with your needs in mind. One of the features that makes this evident is its ability to work as both a cloud-agnostic and a multi-cloud solution. As a cloud-agnostic sol...
What needs improvement with AWS Secrets Manager?
AWS Secrets Manager could not be better because there has been no frustration with the product.
What needs improvement with Microsoft Azure Key Vault?
Based on my three years of experience, I believe there have been no updates to Azure Key Vault. I think the product needs upgrades in terms of access control and certification improvements. While A...
What is your primary use case for Microsoft Azure Key Vault?
Currently, I am not working in Azure cloud, as I work with different products. However, in my previous role, I worked extensively with Azure networking products including Azure Firewall, Virtual Ne...
 

Also Known As

No data available
Microsoft Azure Key Vault, MS Azure Key Vault
 

Overview

 

Sample Customers

Autodesk, Clevy, Stackery
Adobe, DriveTime, Johnson Controls, HP, InterContinental Hotels Group, ASOS
Find out what your peers are saying about AWS Secrets Manager vs. Azure Key Vault and other solutions. Updated: August 2026.
909,153 professionals have used our research since 2012.