IBM HashiCorp Infrastructure Lifecycle Management Reviews

My main use case for IBM HashiCorp Infrastructure Lifecycle Management is infrastructure provisioning and lifecycle management using Terraform. Day-to-day, I use it to provision cloud resources through reusable modules, manage infrastructure changes through version-controlled code, and keep deployments consistent across development, testing, and production environments.

One thing I would add about our main use case is that it gives us better control and visibility over infrastructure changes. It fits well into our CI/CD process, so provisioning and updates are more repeatable, while approvals and version history help reduce the risk of manual changes.

The best features I found most useful in IBM HashiCorp Infrastructure Lifecycle Management are reusable Terraform modules, infrastructure as code with version control, and automated provisioning across environments. I also appreciate the plan and apply workflow because we can review infrastructure changes before deployment and maintain a clear history of what changed.

I rely most on the infrastructure as code feature because it gives us a consistent way to manage infrastructure through version-controlled configuration. It also makes changes easier to preview, reproduce, and roll back compared with making changes manually in the cloud console.

One thing I wish I had understood earlier regarding the features is the importance of designing Terraform modules and state management properly from the beginning. I also find the integration with CI/CD and policy controls valuable because it helps us enforce standards without adding too much manual work.

IBM HashiCorp Infrastructure Lifecycle Management has mainly improved consistency and reduced the time needed to provision and update infrastructure. We have also seen fewer configuration issues because changes go through a standardized version control process instead of being handled manually.

One area for improvement in IBM HashiCorp Infrastructure Lifecycle Management would be making the initial setup and learning curve simpler, especially around Terraform state, modules, and workspace management. Better built-in guidance and troubleshooting for common configuration or deployment errors would make onboarding easier for new team members.

The documentation is generally useful, but some advanced topics can take time to piece together, especially when troubleshooting integrations or complex Terraform configurations. More end-to-end examples and clearer troubleshooting guidance would make the experience easier, particularly for teams adopting it for the first time.

I have been using IBM HashiCorp Infrastructure Lifecycle Management for a little over a year now.

IBM HashiCorp Infrastructure Lifecycle Management has been quite stable for day-to-day infrastructure provisioning and management in our experience. We have had occasional issues with the configuration or integrations, but the platform itself has been reliable enough for our regular development and production workflows.

Scalability with IBM HashiCorp Infrastructure Lifecycle Management has been good in our experience. As we added more environments and cloud resources, we could reuse existing modules and workflows rather than redesigning setup. Scaling mainly involved configuration and capacity adjustments.

Customer support for IBM HashiCorp Infrastructure Lifecycle Management has been generally good, especially for product-specific or technical issues. For more complex Terraform or integration problems, I sometimes rely on documentation and community resources as well, since those can provide more detailed troubleshooting examples.

I would rate the customer support for IBM HashiCorp Infrastructure Lifecycle Management eight out of ten. The response has generally been helpful for product-related issues, although more detailed guidance for complex integrations and troubleshooting would make it stronger.

Before IBM HashiCorp Infrastructure Lifecycle Management, I relied more on manual cloud console provisioning and some custom scripts for infrastructure setup. I moved to HashiCorp because I needed a more standardized, version-controlled approach that could scale across multiple environments.

The pricing for IBM HashiCorp Infrastructure Lifecycle Management was reasonable for the value I received, although the overall cost depends on the deployment model, usage, and the specific HashiCorp capabilities licensed. Setup was fairly manageable, but I did spend some initial effort on architecture, integrations, and establishing Terraform standards.

I have seen a positive ROI mainly through time savings rather than reducing headcount. As a rough estimate, infrastructure provisioning and routine changes take thirty to forty percent less effort, which frees up teams to focus more on higher-value engineering work.

I looked at a few alternatives before choosing IBM HashiCorp Infrastructure Lifecycle Management, mainly AWS CloudFormation, Azure Resource Manager, and compared them around multi-cloud support, ease of managing infrastructure as code, reusable components, teamwork flow, and integration with our existing CI/CD processes.

I would recommend to others looking into IBM HashiCorp Infrastructure Lifecycle Management that they define their infrastructure standards, module structure, and state management approach before rolling it out widely. Also, start with a few repeatable use cases, integrate it with your CI/CD pipeline, and gradually expand once the team is comfortable with Terraform.

Overall, IBM HashiCorp Infrastructure Lifecycle Management has been a practical solution for standardizing infrastructure management and reducing manual provisioning work. The main thing I would emphasize is to invest time upfront in module design, state management, and governance, because that makes the platform much easier to scale later. I would rate this solution eight out of ten overall.

Our main use case for IBM HashiCorp Infrastructure Lifecycle Management is standardizing and automating the lifecycle of cloud infrastructure using IaC, mainly for AWS environments. We have multiple environments and a number of AWS services that need to be provisioned consistently. Instead of having our engineers manually create resources through the AWS console, we use a Terraform-based infrastructure definition so that the infrastructure can be reviewed and version controlled and reproduced anytime. The important part is not simply creating an EC2 instance or VPC with Terraform, but having a consistent process for building, changing, reviewing, and eventually removing infrastructure. IBM HashiCorp Infrastructure Lifecycle Management positions infrastructure lifecycle management around a standardized workflow for provisioning, managing, and governing infrastructure with Terraform at the center of this workflow.

A quick, specific example of how I have used it in a real situation involves our IaC workflows, mainly Terraform, for both new infrastructure changes and existing infrastructure. A typical workflow includes Terraform configuration, then review, plan, approval, and application, resulting in the AWS infrastructure being up. This provides us with a much more controlled process than manually making infrastructure changes. For example, if we need to create a new application environment, we can reuse the same infrastructure patterns while changing environment-specific variables, which helps avoid situations where development, staging, and production become configured differently. We maintain a reusable Terraform configuration or module for common components, allowing us to standardize VPC definitions rather than having every application team define a VPC differently, which significantly simplifies the infrastructure review process. One practical benefit is that infrastructure changes become visible before they are applied, giving us an opportunity to review what is going to change before applying it, particularly useful in production.

The best features IBM HashiCorp Infrastructure Lifecycle Management offers include standardization, which I find most valuable. Terraform is powerful, but the real operational value comes from having a consistent lifecycle around the infrastructure. Instead of trying to remember how someone created an AWS resource six months ago, I can look at the infrastructure definition and understand how it is supposed to be managed. Other major benefits include repeatability; if we need another environment, we do not have to start from scratch.

Standardization and repeatability have greatly helped my team and projects. Rather than having every application team define the VPC differently, we can standardize it and use that standardization everywhere, leading to a more consistent infrastructure. This consistency makes it much easier to provision the infrastructure each time and saves us a significant amount of time.

IBM HashiCorp Infrastructure Lifecycle Management has positively impacted my organization by significantly reducing manual infrastructure work. Before standardizing our infrastructure as code workflows, creating an environment involved extensive manual efforts, AWS console work, and documentation. With reusable Terraform configurations, much of that process becomes repeatable and results in faster environment creation. Once the required modules and variables are available, setting up another environment is much easier. Consistency has improved, troubleshooting is simpler, change control is better, and disaster recovery is easier now.

IBM HashiCorp Infrastructure Lifecycle Management can be improved with easier onboarding, as newcomers to Terraform and the HashiCorp ecosystem may find it challenging to understand and complete the workflow. Additionally, better visibility for large environments is needed, as managing many AWS accounts and thousands of resources complicates understanding the relationships between infrastructure components. While reusable modules are extremely useful, organizations require a solid process for versioning, testing, and upgrading those modules, which can become a significant operational task in large Terraform environments.

I have been using IBM HashiCorp Infrastructure Lifecycle Management for around one year.

IBM HashiCorp Infrastructure Lifecycle Management is stable.

IBM HashiCorp Infrastructure Lifecycle Management is scalable.

Customer support for IBM HashiCorp Infrastructure Lifecycle Management is good.

I previously used different solutions, having evaluated self-managed Terraform workflows and internal Terraform modules.

I have seen a return on investment, particularly in terms of time saved, as previously mentioned regarding reusability and standardization; time saved is a key metric.

I would evaluate the pricing based on the amount of infrastructure and engineering time being managed. For a small workload environment, justifying the cost can be harder if the team is already comfortable managing Terraform independently. For larger organizations, the value comes from standardization, governance, and reduced manual workflows. For us, the productivity and consistency benefits are more important than simply comparing IBM HashiCorp Infrastructure Lifecycle Management against the cost of running Terraform itself.

Before choosing IBM HashiCorp Infrastructure Lifecycle Management, I evaluated other options including self-managed Terraform workflows and internal Terraform modules.

I would advise others looking into using IBM HashiCorp Infrastructure Lifecycle Management that if you have a complex infrastructure where maintainability and standardization become valuable, this is a good tool to use. I would rate this product a 9 out of 10.

My main use case for IBM HashiCorp Infrastructure Lifecycle Management is that I am using it under Terraform, where I am provisioning infrastructure over the cloud.

A quick, specific example of how I use IBM HashiCorp Infrastructure Lifecycle Management for asset class management or provisioning infrastructure for the cloud is that Terraform is very useful to provision infrastructures as per requirement time to time, and when I need to provision infrastructures over the cloud, I can just use Terraform.

IBM HashiCorp Infrastructure Lifecycle Management has positively impacted my organization as it has been very beneficial for us for quick provisioning of infrastructure since I have been using it for the last two years.

I have not considered specific improvements in speed, efficiency, or cost savings since using IBM HashiCorp Infrastructure Lifecycle Management; however, it saves time while creating infrastructure through the particular cloud-based UI, and as compared to that, Terraform gives a fast provisioning of infrastructure.

The best features IBM HashiCorp Infrastructure Lifecycle Management offers include being open source, so everyone is ready to use it if they want, and of course, they have enterprise service as well, which means there are two options available: either you can go with open source or you can go as a SaaS model.

Regarding IBM HashiCorp Infrastructure Lifecycle Management's AI capabilities, I think its governance and security are good as it compiles governance and security policy without any hurdles.

Regarding IBM HashiCorp Infrastructure Lifecycle Management's AI capabilities, I think the accuracy and reliability of its output are overall good.

I have no comment on how IBM HashiCorp Infrastructure Lifecycle Management can be improved as of now.

I cannot comment on anything that could be better, even if it is something small, such as documentation, support, or a feature I wish was there.

I feel it is not a perfect ten because, as of now, I am using only the open source version where I have encountered some tricky options, and I still require some AI contribution while creating infrastructures; as of now, it is very hard-coded and involves other manual tasks, which is why I am choosing eight, not ten.

I have been using IBM HashiCorp Infrastructure Lifecycle Management for the last three years.

IBM HashiCorp Infrastructure Lifecycle Management is stable in my experience.

Regarding the scalability of IBM HashiCorp Infrastructure Lifecycle Management, I am currently not using it for scalability, as this is a standalone and user-specific client, so scalability is not a part of what I am using as of now.

I have not contacted customer support for IBM HashiCorp Infrastructure Lifecycle Management yet; whenever an issue occurs, I try to solve it on my end.

I have not previously used a different solution before IBM HashiCorp Infrastructure Lifecycle Management; as for now, this is the first solution we are looking to use, which is Terraform for provisioning the infrastructure.

I have not seen a return on investment with IBM HashiCorp Infrastructure Lifecycle Management, and I cannot share any relevant metrics such as time saved or money saved.

I have not purchased IBM HashiCorp Infrastructure Lifecycle Management through the AWS Marketplace yet; as mentioned, I am currently using the open source version.

My experience with IBM HashiCorp Infrastructure Lifecycle Management regarding pricing, setup cost, and licensing is that I am not using a license; currently, I am using the open-source product.

I have not evaluated any other options before choosing IBM HashiCorp Infrastructure Lifecycle Management; as I mentioned, this is my first one.

IBM HashiCorp Infrastructure Lifecycle Management is deployed in a mixed environment in my organization, as I have a public and hybrid cloud; however, I am mainly using Terraform under the public cloud only, not a hybrid one.

The cloud providers I use for my public cloud deployment are both AWS and Azure.

My advice for others looking into using IBM HashiCorp Infrastructure Lifecycle Management is that it is organization-specific and requirement-specific, such as if they are looking for any tool to adopt or not.

I would rate IBM HashiCorp Infrastructure Lifecycle Management an eight on a scale of one to ten.

I am working in a platform team where we manage an internal developer platform with lots of workloads around AWS EKS and GCP GKE. We use Terraform to provision infrastructure across those cloud setups. Terraform allows us to create infrastructure as code to have a central place where all configurations are stored with all infrastructure setups.

Recently, we had a requirement from a customer, which is a developer team. They needed to deploy an application in a specific, dedicated AWS EKS cluster. We had to create that cluster and configure the networking and all cluster bootstrap modules that we needed to set up. We provisioned the AWS EKS cluster using Terraform and our reusable Terraform modules that we use to provision our infrastructure across the cloud environment.

Since we have specific Terraform modules for each infrastructure setup, we can reuse those modules in our infrastructure repository and provision a cluster within a few minutes rather than rewriting all infrastructure configurations. This is particularly helpful for us as a platform team managing an internal developer platform with many customers.

Our platform engineers' productivity has improved significantly with the ability to manage all infrastructure as code. We have that code and know what is in our cloud setup rather than logging into the cluster to check it.

Before using Terraform, our team used manual setup to create clusters in AWS using the AWS console, which would extend into two to three sprints for one person to set up all those components. With Terraform and those reusable modules, we were able to minimize it to two to three days with all verifications included.

The best features IBM HashiCorp Infrastructure Lifecycle Management offers include having a central place with reusable templates. Since this is a multi-cluster setup, coordinating a shared change safely is essential. Most of the time, there are infrastructure patterns in a platform, so we need a repeatable way to use them across environments.

Since we manage a separate Terraform modules repository for our configurations with AWS EKS cluster configurations and HashiCorp Vault configurations, if we need to make a change across all clusters, we only need to change that Terraform module itself.

Another benefit is that it can be used not only for a specific cloud setup. We can use it for AWS, GCP, and also for Azure. The multi-cluster, multi-cloud setup capability using Terraform is a good feature.

For platform teams, I would appreciate an easier way to manage changes across a large set of accounts and clusters. I would want to see the impact across all targets, review the plans individually, and roll out changes in controlled stages from one place. That would be a good improvement for Terraform for a platform team.

I have been using IBM HashiCorp Infrastructure Lifecycle Management for around three years. Before working in my current role, I used Terraform since my university life when I was studying at Colombo University for personal projects. My total experience is now three years.

In our company, since we have a governance body on top, we have no idea where these costs are determined. What we do is use them from the lower setup.

I would say IBM HashiCorp Infrastructure Lifecycle Management deserves a nine out of ten marks. With the improvement I mentioned for platform teams, that would be really valuable. Apart from that, overall, it definitely deserves this rating.

I have not worked with IBM HashiCorp Infrastructure Lifecycle Management's AI capabilities and have not explored them yet. Most of the time, we used GitHub Copilot or Codex to generate code for Terraform. My experience with the AI capabilities of Terraform is limited.

For anyone using HashiCorp Terraform, I would suggest using reusable templates and Terraform modules to minimize code repeatability.

I have implemented HashiCorp Vault for secret management.

In my opinion, the role of Vault in data security compliance is not much of a concern at this time, as this is just a testing phase where I deployed a couple of environments for different clients. Definitely, maybe in the 2027 to 2028 financial year, I have a compliance audit for that.

In assessing the effectiveness of HashiCorp Consul in managing service networking, I find that we are not frequently using a GUI; we just use a CLI perspective.

I do not use HashiCorp Nomad for workload orchestration at this time.

I am mainly using Terraform, and it has helped me manage multi-cloud environments.

In my opinion, HashiCorp can be improved because there are a couple of things they need to improve. When we talk about the local providers in Terraform, it is very difficult to use that.

I can give a little more detail on the kind of problems I am facing. When I use a local provider for a hybrid cloud, which is just a local server setup over VMware and other things, it is very difficult to provision the server and write the code.

HashiCorp [Private Offer Only] could do something about it by requiring some recommendation steps.

I do not remember exactly what additional features I would like to see in the next release to make it closer to ten, though code optimization was mentioned.

As of now, I have been working with HashiCorp Security Lifecycle Management only using HashiCorp Terraform, which is open-source.

I believe the overall technical support is good, and they should improve response time, first-level support quality, and overall competence.

In terms of pricing, I find the HashiCorp price a little higher. That needs to be optimized.

I am using version 1 point something of HashiCorp, and I do not exactly remember the version.

I have not been a partner or reseller of HashiCorp; this is just a customer relationship.

From my perspective, I would rate HashiCorp eight out of ten overall.