I would advise doing a Proof of Concept first and then deciding accordingly because your use case might be simple. You can try out AWS Key Management or Azure Key Vault. They are different products. Do the POC and then decide what you need. Overall, I would rate the solution a six out of ten. No solution is a ten in my opinion.
Go for it! It's essential for adopting a zero-trust architecture, especially in hybrid setups combining multiple cloud providers with on-premises infrastructure. You should have a centralized location for your secret data, not storing it in files that could be accidentally uploaded to versioning tools like Git. Hardcoded credentials are a no-go. Centralize with a solution like HashiCorp Vault. Overall, I would rate the solution a ten out of ten.
Chief Technical Director at LondonLink OTC Limited
Real User
Top 5
2023-08-25T12:18:28Z
Aug 25, 2023
I rate HashiCorp Vault an eight out of ten. It is a good product to consider for companies who are looking to build on-premise or hybrid infrastructure.
I rate HashiCorp Vault a nine out of ten. The goal is to move towards open source, so it's always good to have a cloud agnostic-based solution. This is why our organization is always goes with a hybrid solution, which doesn't depend on any single cloud provider—it's always good to look for cloud agnostic solutions. In that view, I think that HashiCorp solutions are very, very acceptable.
My previous organization was using this solution, whereas the current organization I work for is not. This is due to the fact that we work on multiple projects. We are a research team, and the delivery team does the implementation. We just propose solutions to clients based on their particular requirements. We tend to use many different solutions and tools at this company. I'd rate the solution at a six out of ten.
Founder & Principal Architect at NCompas Business Solutions Inc.
Real User
2021-03-16T23:00:21Z
Mar 16, 2021
Be careful about how you structure your Terraform scripts. You should probably start off with some examples already given by HashiCorp before you begin implementation. Once you've gone too deep, it's difficult to factor things in and out of it. Carefully read the documentation right from the get-go. Overall, on a scale from one to ten, I would give HashiCorp Vault a rating of eight.
One of the questions that I have been trying to solve is whether it is possible to update the cloud AWS keys from the on-premises solution. I have been through the documentation and the blogs and still do not know whether it is possible. Definitely, they can be managed once they have been deployed into the cloud, but I want to know the other way around. Our intention is ultimately to deploy on-premises, which is why this is important. My advice for anybody who is implementing this solution is to fully go through the documentation and understand all of the use cases before implementing it. I would rate this solution a seven out of ten.
HashiCorp Vault is a cloud-agnostic solution used for security and secret management. Its valuable features include integration with other HashiCorp tools, token sharing, open source nature, cloud agnosticism, and on-the-fly encryption management.
The solution provides encryption of data at rest, in use, in transit, on the fly, and linked with applications. It is free to use, and the interface is simple to navigate. HashiCorp Vault has helped organizations with its multiple...
I would advise doing a Proof of Concept first and then deciding accordingly because your use case might be simple. You can try out AWS Key Management or Azure Key Vault. They are different products. Do the POC and then decide what you need. Overall, I would rate the solution a six out of ten. No solution is a ten in my opinion.
I would rate the overall solution an eight out of ten.
Go for it! It's essential for adopting a zero-trust architecture, especially in hybrid setups combining multiple cloud providers with on-premises infrastructure. You should have a centralized location for your secret data, not storing it in files that could be accidentally uploaded to versioning tools like Git. Hardcoded credentials are a no-go. Centralize with a solution like HashiCorp Vault. Overall, I would rate the solution a ten out of ten.
I rate HashiCorp Vault a nine out of ten. It is a good product and doesn’t necessarily require using TerraForm for cloud infrastructure.
I rate HashiCorp Vault an eight out of ten. It is a good product to consider for companies who are looking to build on-premise or hybrid infrastructure.
I recommend the solution to others and rate it an eight out of ten.
I would rate it a nine out of ten.
I rate HashiCorp Vault a nine out of ten. The goal is to move towards open source, so it's always good to have a cloud agnostic-based solution. This is why our organization is always goes with a hybrid solution, which doesn't depend on any single cloud provider—it's always good to look for cloud agnostic solutions. In that view, I think that HashiCorp solutions are very, very acceptable.
My previous organization was using this solution, whereas the current organization I work for is not. This is due to the fact that we work on multiple projects. We are a research team, and the delivery team does the implementation. We just propose solutions to clients based on their particular requirements. We tend to use many different solutions and tools at this company. I'd rate the solution at a six out of ten.
Be careful about how you structure your Terraform scripts. You should probably start off with some examples already given by HashiCorp before you begin implementation. Once you've gone too deep, it's difficult to factor things in and out of it. Carefully read the documentation right from the get-go. Overall, on a scale from one to ten, I would give HashiCorp Vault a rating of eight.
One of the questions that I have been trying to solve is whether it is possible to update the cloud AWS keys from the on-premises solution. I have been through the documentation and the blogs and still do not know whether it is possible. Definitely, they can be managed once they have been deployed into the cloud, but I want to know the other way around. Our intention is ultimately to deploy on-premises, which is why this is important. My advice for anybody who is implementing this solution is to fully go through the documentation and understand all of the use cases before implementing it. I would rate this solution a seven out of ten.