The primary use case for HashiCorp Consul is in a microservices architecture, particularly within a premium application involving various streaming services like Kafka.
External reviews
46 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Has an efficient key vault feature, but its integration capabilities need enhancement
What is our primary use case?
What is most valuable?
The product's most valuable features are support for Service Mesh TLS and canary deployment.
What needs improvement?
They could improve issues related to triggering generic deployments for the platform. We have raised multiple support cases. They could enhance the integration approach with Service Mesh tools. Additionally, the UI needs enhancement.
For how long have I used the solution?
We have been using HashiCorp Consul for 13 months.
What do I think about the stability of the solution?
The platform is stable. However, it needs maintenance and monitoring as it sometimes encounters downtime.
What do I think about the scalability of the solution?
We have implemented the product in two of our projects.
How are customer service and support?
The feedback provided by the technical support team doesn't resolve the issue.
Which solution did I use previously and why did I switch?
Compared to other products, HashiCorp Consul is more flexible to use.
How was the initial setup?
The platform is easy to install when integrated with Kubernetes. The ideal setup includes running three workers or additional nodes for data persistence, especially when Consul is deployed in an on-premises environment. Even when deploying on EKS, the reports run smoothly as scheduled shifts.
What's my experience with pricing, setup cost, and licensing?
In case of budget constraints, we opt for the product's business support licenses and use an open-source version. However, it is advisable to go for the enterprise edition.
What other advice do I have?
I recommend HashiCorp Consul for beginners. It is a stable tool. The key-vault storage feature has significantly enhanced our configuration management process. We have maintained the secret software applications in the vault and retrieved the information from Kv.
I rate the product a seven out of ten. It is good open-source software to be managed within the production.
Safe, secure and Trustworthy
What do you like best about the product?
We have used Hashicorp Vault forever now and we have had no issues with it in terms of security of our data. The documentations also make it very easy to use.
Its integration with terraform and other tech is pretty straightforward.
Its integration with terraform and other tech is pretty straightforward.
What do you dislike about the product?
Nothing off the top of my head. Its actually the best given its competitors.
What problems is the product solving and how is that benefiting you?
HashiCorp Vault helps us save all our important passwords without the hassle of losing them to hackers.
A scalable solution that can be used to perform health checks of applications and services
What is our primary use case?
I use the solution for service discovery and orchestration. We have a lot of microservices architecture.
What is most valuable?
The solution is useful for performing health checks of the applications and services. The documentation is good.
What needs improvement?
Health check outputs are delayed sometimes. If a service is down for more than five or ten seconds, sometimes the tool is not able to capture it.
For how long have I used the solution?
I have been using the solution for more than four to five years. I am using the latest version of the solution.
What do I think about the stability of the solution?
The tool’s stability is good. I rate the stability a nine out of ten. We had some issues. Sometimes, health checks do not give the right outcome.
What do I think about the scalability of the solution?
The tool’s scalability is good. I rate the scalability a nine out of ten. We have not faced any issues in scaling the server. We run the server behind an autoscaling group. Our backup and restore mechanism is very strong. Specific teams in our organization that follow the microservices architecture use the solution a lot. We have less than 20 users.
Which solution did I use previously and why did I switch?
We were planning to use Istio. Another team in our organization was using Envoy. We were already using the enterprise version of Terraform. So, we decided to use Consul.
How was the initial setup?
The initial setup is moderately easy. I do the configuration using Chef. We deploy the solution on Amazon EC2 instances. Everything is automated. We spent some time in the HA setup. Other than that, it doesn’t take much time.
What other advice do I have?
I take care of the infrastructure. I use Chef for configuration management. I work on multiple technologies. Overall, I rate the product an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Great for securing sensitive information
What do you like best about the product?
Vault provides amazing central place to keep secrets securely and manage the key values easily throgh beautiful user interface. The APIs are also easy to use.
What do you dislike about the product?
It takes time to learn the Vault so there is high learning curve.
What problems is the product solving and how is that benefiting you?
It stores secret in the Vault securely and easy to manage them.
Improves security protocols
What do you like best about the product?
Capability of encrypting files and handling loads is commendable. The ability to create sections tailored for document types is good. Its flexibility is incredibly valuable.HashiCorp Vault stands as a powerful tool for securing sensitive information.
What do you dislike about the product?
The initial setup and configuration process is complex and time consuming for organizations.
What problems is the product solving and how is that benefiting you?
HashiCorp Vault is storing and managing sensitive information solving this problem. Its strong encryption mechanisms and access control features ensure data protection.
Hashicorp Vault Review
What do you like best about the product?
The vault setup process is quite easy. The backend engines are very useful for integrating authentication and authorization of existing services like Kubernetes. The path based secret storage is great where RBAC can be integrated for better security.
What do you dislike about the product?
The usage of vault can be bit complex to understand for beginners.
What problems is the product solving and how is that benefiting you?
The secret storing with different application teams having isolated paths. Role based access control to restrict access to specific teams according to the team role and secrets required. Versioning of secrets is a feature very frequently used for rotation of secrets.
Complex yet essential for saas based companies
What do you like best about the product?
The community and the overall functionality it provides, are easy to integrate with LDAP and OIDC, and it supports almost all the top secret management providers like AWS KMS and Google KMS. Its open-source nature of it enables other developers to create tools for Vault which is fantastic.
What do you dislike about the product?
Some of the documentation is very poor, especially when I was trying to integrate Keycloak I cannot find a good documentation.
What problems is the product solving and how is that benefiting you?
The secret sprawl in the companies, storing it in base64 cannot provide security hence Vault solves this by providing encryption and tons of other features like its seal/unseal method.
Does what it needs to in the best way possible
What do you like best about the product?
it integrates with so many services, key being GitHub Action for me.
What do you dislike about the product?
Identifying tokens can be a bit of a hassle, and requires mulitple API calls to properly delete a key from a user-friendly identifier.
What problems is the product solving and how is that benefiting you?
Sharing secrets across multiple services.
It's a versatile, and secure solution for managing secrets in production
What do you like best about the product?
One of the things I appreciate about HashiCorp Vault is its versatility. It supports a wide range of authentication methods, including tokens, user-pass, and LDAP, allowing us to choose the method that best suits our needs. The platform also supports dynamic secrets generation, making it easier to manage secrets at scale.
What do you dislike about the product?
While HashiCorp Vault is a robust and reliable solution for managing secrets, some users may find it challenging to set up and configure, particularly for more complex use cases. Additionally, some users may find the pricing model to be a bit expensive, especially for smaller teams or organizations with limited budgets.
What problems is the product solving and how is that benefiting you?
HashiCorp Vault solves the business problem of securely storing, managing, and distributing sensitive data and secrets such as API keys, passwords, and certificates across distributed systems and applications in production environments. By offering end-to-end encryption, access controls, and a user-friendly interface, Vault helps businesses keep their secrets safe and secure from unauthorized access and breaches.
Useful software to store our third party software passwords
What do you like best about the product?
We can store our third-party software passwords and retrieve them easily. We can also give vault access to users to recover certificates and passwords through PAT tokens from GHE.
What do you dislike about the product?
As of now, nothing. We can satisfy the basic necessity of retrieving passwords for our nexus repository. Most of the team members use it for that purpose alone so no concerns have been raised.
What problems is the product solving and how is that benefiting you?
We can store important passwords for our repository and codes for our proxy setup within our project. Since we work in a bank account, the passwords need to be protected, and the codes need to be stored safely. We can also grant access through PAT token, so anyone accessing will automatically be authorized as they are part of GHE.
showing 1 - 10