The usual use cases for HashiCorp Terraform that I work with mostly include automating tasks such as provisioning resources and creating resources over the clouds. If we want to create an EC2 instance on AWS, we have to log into EC2 and follow specific steps for creating instances. Creating thousands of EC2 instances with the same configuration requires repeating those steps, which can lead to mistakes. But using HashiCorp Terraform helps us by enabling infrastructure as code, allowing us to create infrastructure using code. We can write simple code, and based on that, we can create multiple instances with a single run of code. HashiCorp Terraform also supports multi-cloud developments, allowing us to work with AWS, Azure, Google, and Oracle simultaneously. It enables immutable infrastructure, and after HashiCorp Terraform creates resources, a state file is generated that stores metadata, which we can control using version control, allowing us to revert to previous versions if needed.
At Remessa, we use HashiCorp Terraform for everything involving infrastructure. We use HashiCorp Terraform to manage our repository on GitHub, to manage permissions, invitations, and teams. We use HashiCorp Terraform to manage our AWS infrastructure, DNS, policies on Cloudflare. We use HashiCorp Terraform to manage our alerts on PagerDuty, and we set up some things on Grafana with other services. We use GitOps, so when we need to make changes such as upgrading our databases when a new Postgres version is released, we can see the version of each database that worked, allowing us to manage the process effectively. We can see in the state that our main database will be upgraded immediately. We can prevent breaks or issues because of the states, which allows us to schedule a window time for upgrades when needed.
Cloud Architect at a tech vendor with 10,001+ employees
Real User
Top 20
May 26, 2025
We primarily use HashiCorp Terraform for our infrastructure deployments and cloud deployments. As a cloud architect and infra DevOps architect, we use HashiCorp Terraform to deploy our code, builds, and set up CI/CD pipelines. We create Terraform code and deploy it through Terraform Enterprise. Regarding state management and orchestration capabilities of HashiCorp Terraform's impact on our workflows, we had two different environments. Initially, we used Jenkins for our CI/CD pipelines. Because we primarily work on Azure, we use remote state files for Azure deployments. Jenkins runs the HashiCorp Terraform code, and then the state file gets saved in our Azure storage as a remote location. Whenever we require that state file, we can retrieve it from there. At a later stage, we enhanced the environment by setting up Terraform Enterprise in our environment. Currently, we have it within our environment. We set up Terraform Enterprise with HashiCorp's license. We create modules from HashiCorp Terraform using the Azure ARM provider, and then we set up those modules to apply Azure best practices. We provide this to the development team and other teams so they can reuse these modules and deploy secure codes. We also manage upgrades and the complete lifecycle of TFE, and we provide these services to our other teams.
CTO at a computer software company with 201-500 employees
Reseller
Top 5
Jan 7, 2025
I use it to deploy our Kubernetes clusters and Boomi as well. I can run Boomi by itself and not worry about Terraform and Kubernetes, and that's okay. However, my use case requires me to run it in a cluster environment to scale up and scale down accordingly and manage costs. This is why I chose Kubernetes. Although it's possible to manually roll it out, I have security requirements to consider for a secure environment. To make it repeatable, I use Bicep or Terraform, as I'm mostly running in Azure. I decided on Terraform to manage deployments across multiple environments. This includes a dev environment, a QA environment, and now a production environment. I test and then run Terraform to deploy these environments. In AI, it's more about setting up your environment. I develop AI-based products and use Terraform to create a consistent and secure environment in Azure. Once deployed, I get a security score from Azure and receive recommendations for improvements. If a resource is noncompliant under SOC 2, type one or two, ISO, or HIPAA, I make the changes in Terraform, redeploy, and observe score improvements. Terraform aids in ensuring my deployments are correctly configured across environments.
The primary use case for Terraform is the deployment of infrastructure as a code, creating pipelines, and deploying scripts for services like VPC, EC2, and other AWS services. I also use Terraform for managing multi-cloud environments, easily connecting with services like AWS, Azure, and GCP.
I used HashiCorp Terraform primarily as infrastructure as code. It allows you to create, modify, and delete infrastructure resources. This includes tasks such as manually creating instances in the console or automating infrastructure deployment.
IT Consultant at a tech vendor with 1-10 employees
Consultant
Top 5
Jun 6, 2024
We use HashiCorp Terraform for Infrastructure as Code. It automates the deployment of infrastructure within the Azure platform. Terraform can manage almost all aspects of infrastructure provisioning. If there are tasks that Terraform cannot perform directly, you can use the Azure CLI or other tools and call them from within Terraform scripts.
HashiCorp Terraform is primarily used to manage infrastructure. It is responsible for creating and managing infrastructure components. For example, when we initially designed the infrastructure for this project, we started by designing the VPC. We decided to use a specific region-based VPC. We specified the number of public and private subnets, as well as setting up Internet gateways and NAT gateways, all using Terraform. Once the infrastructure was set up, we deployed our resources, such as ECS containers, ECS tasks, and RDS databases, in private subnets, all properly managed by Terraform. However, we use GitHub Actions for CI/CD pipeline purposes. While Terraform handles the infrastructure management, GitHub Actions manages the CI/CD pipeline for our ECS clusters. In my previous project, we used Jenkins, but in this project, we use GitHub Actions for deployment, testing, and other pipeline tasks.
I use the solution in my company to create services over cloud platforms. I have used HashiCorp Terraform for GCP, Azure, and AWS to create resources. With HashiCorp Terraform, it is easy to manage resources in a single file.
Co Founder and Technical Architect at Think NYX Technologies LLP
Real User
Top 5
Jan 6, 2021
Initially, We have started using Terraform for provision cloud infrastructure and slowly our requirement keep growing up currently my team is using Terraform for managing AWS/Azure/GCP or I should multiple clouds along with Kubernetes/Rancher, Gitlab, MySQL/Oracle, datadog.
We use Terraform for many different use cases. The primary one is ensuring that the security policy is automatically applied to all of the resources within a cloud environment. Another one would be creating and dismantling all sorts of test labs, as well as creating a development environment. We found a way to automatically create a development environment only for the time we need. We develop the infrastructure and cloud-related tasks.
Terraform is our main infrastructure as code at the bank. Our entire deployment site and the AWS solution are based on Terraform. We use EBridge and the Dochub solution on the Bitbucket pipeline. Terraform runs on a container in the Bitbucket pipeline, but to create my entire cloud solution, I use EBridge.
Our primary use for the solution is to create infrastructure on the cloud. We are a cloud integrator. We write our codes in Terraform and reuse them for multiple customers by changing the values.
We use HashiCorp Terraform orchestration tool for infra provisioning (mostly servers), both in the cloud and on-premise environments. This allows for VM provisioning, networking, and storage management, especially in a cloud environment where we have many servers that can't be provisioned one by one.
Cloud and DevOps Architect at a tech services company with 10,001+ employees
Real User
Jan 12, 2023
Our company uses the solution to deploy resources and infrastructure in Azure Cloud via the Azure DevOps pipelines. We have two developers who use the solution.
Senior Software Engineer at a retailer with 10,001+ employees
Real User
Jan 10, 2023
HashiCorp Terraform is a tool used for provisioning cloud infrastructure. It is used in this specific use case to deploy and provision all services, including Kafka, MongoDB, and Postgres clusters, using infrastructure as code.
Senior Build And Release Engineer at a tech services company with 1,001-5,000 employees
Real User
Oct 4, 2022
We use HashiCorp Terraform to set up AWS infrastructure, and sometimes Cloudflare. It is not exactly a tool for configuration, it is for setting up the development of the infrastructure.
HashiCorp Terraform is a binary executable file, that you can download to your PC and manage any cloud solution in the world, such as Google Cloud Platform, Amazon AWS, OpenStack, CloudStack, or VMware. When you use DevOps in your company, it's a useful tool for it.
Chief Technology and Strategy Officer at The White House
Real User
Feb 22, 2022
A primary use case of Terraform is for deploying a VM on a cloud using Terraform script. If I then want to deploy a third-party toolset, a solution such as Aviatrix can create an overlay on top of each of the cloud providers and you can connect the clouds together. I'm a solutions architect and we are customers of HashiCorp.
Co Founder and Technical Architect at Think NYX Technologies LLP
Real User
Top 5
Jan 4, 2021
We are using Terraform to manage our multi-cloud requirement for different demos and test environments. It helps us set up the entire environment in a few mins with the exact configuration in AWS, Azure, or GCP, along with other setups like a database, Kubernetes, etc.
Sr. Systems Engineer / Tech Logic Consultant. at a non-tech company with self employed
Real User
Nov 13, 2020
I mainly use it for infrastructure automation. I use it to provision servers in different cloud providers and in-house with the principles to create a Kubernetes cluster. If you have a master node concept I would create the master and find related text. The main function for me is to create infrastructure.
We deliver the platform as a service to businesses. For example, one request for a particular subscription could be in the business domain or non-business domain, whatever it may be, based on the demand, we deliver the customized subscription to them. For each service, we have different constraints. What needs to be delivered in the VNet of Azure, and what needs to be done externally.
We use it to provision cloud infrastructure. We use it to provision all kinds of infrastructure from wherever we want, we Terraform to the cloud. We provision new infrastructure, we update existing infrastructure with it, we manage our DNS records, and also deploy new applications on Kubernetes. That's the main use, but we use it for all of our infrastructures, so it has a lot of different use cases.
HashiCorp Terraform is a powerful configuration management solution that aims to provide users with the ability to maximize the ease with which users can perform their configuration management operations. It makes it so that organizations can reliably configure and manage their infrastructure. Terraform is a tool that transforms every user into an administrator and project collaborator. Businesses that use it have at their command a solution that they can use for the entire lifecycle of...
The usual use cases for HashiCorp Terraform that I work with mostly include automating tasks such as provisioning resources and creating resources over the clouds. If we want to create an EC2 instance on AWS, we have to log into EC2 and follow specific steps for creating instances. Creating thousands of EC2 instances with the same configuration requires repeating those steps, which can lead to mistakes. But using HashiCorp Terraform helps us by enabling infrastructure as code, allowing us to create infrastructure using code. We can write simple code, and based on that, we can create multiple instances with a single run of code. HashiCorp Terraform also supports multi-cloud developments, allowing us to work with AWS, Azure, Google, and Oracle simultaneously. It enables immutable infrastructure, and after HashiCorp Terraform creates resources, a state file is generated that stores metadata, which we can control using version control, allowing us to revert to previous versions if needed.
At Remessa, we use HashiCorp Terraform for everything involving infrastructure. We use HashiCorp Terraform to manage our repository on GitHub, to manage permissions, invitations, and teams. We use HashiCorp Terraform to manage our AWS infrastructure, DNS, policies on Cloudflare. We use HashiCorp Terraform to manage our alerts on PagerDuty, and we set up some things on Grafana with other services. We use GitOps, so when we need to make changes such as upgrading our databases when a new Postgres version is released, we can see the version of each database that worked, allowing us to manage the process effectively. We can see in the state that our main database will be upgraded immediately. We can prevent breaks or issues because of the states, which allows us to schedule a window time for upgrades when needed.
We primarily use HashiCorp Terraform for our infrastructure deployments and cloud deployments. As a cloud architect and infra DevOps architect, we use HashiCorp Terraform to deploy our code, builds, and set up CI/CD pipelines. We create Terraform code and deploy it through Terraform Enterprise. Regarding state management and orchestration capabilities of HashiCorp Terraform's impact on our workflows, we had two different environments. Initially, we used Jenkins for our CI/CD pipelines. Because we primarily work on Azure, we use remote state files for Azure deployments. Jenkins runs the HashiCorp Terraform code, and then the state file gets saved in our Azure storage as a remote location. Whenever we require that state file, we can retrieve it from there. At a later stage, we enhanced the environment by setting up Terraform Enterprise in our environment. Currently, we have it within our environment. We set up Terraform Enterprise with HashiCorp's license. We create modules from HashiCorp Terraform using the Azure ARM provider, and then we set up those modules to apply Azure best practices. We provide this to the development team and other teams so they can reuse these modules and deploy secure codes. We also manage upgrades and the complete lifecycle of TFE, and we provide these services to our other teams.
I use it to deploy our Kubernetes clusters and Boomi as well. I can run Boomi by itself and not worry about Terraform and Kubernetes, and that's okay. However, my use case requires me to run it in a cluster environment to scale up and scale down accordingly and manage costs. This is why I chose Kubernetes. Although it's possible to manually roll it out, I have security requirements to consider for a secure environment. To make it repeatable, I use Bicep or Terraform, as I'm mostly running in Azure. I decided on Terraform to manage deployments across multiple environments. This includes a dev environment, a QA environment, and now a production environment. I test and then run Terraform to deploy these environments. In AI, it's more about setting up your environment. I develop AI-based products and use Terraform to create a consistent and secure environment in Azure. Once deployed, I get a security score from Azure and receive recommendations for improvements. If a resource is noncompliant under SOC 2, type one or two, ISO, or HIPAA, I make the changes in Terraform, redeploy, and observe score improvements. Terraform aids in ensuring my deployments are correctly configured across environments.
The primary use case for Terraform is the deployment of infrastructure as a code, creating pipelines, and deploying scripts for services like VPC, EC2, and other AWS services. I also use Terraform for managing multi-cloud environments, easily connecting with services like AWS, Azure, and GCP.
I used HashiCorp Terraform primarily as infrastructure as code. It allows you to create, modify, and delete infrastructure resources. This includes tasks such as manually creating instances in the console or automating infrastructure deployment.
I use the solution to provision cloud resources on Azure, AWS, and GCP platforms.
We use the product for cloud deployments, specifically provisioning services in the cloud.
It is a useful configuration management solution. DevOps practices are a main tool for infrastructure as a code.
We use HashiCorp Terraform for Infrastructure as Code. It automates the deployment of infrastructure within the Azure platform. Terraform can manage almost all aspects of infrastructure provisioning. If there are tasks that Terraform cannot perform directly, you can use the Azure CLI or other tools and call them from within Terraform scripts.
HashiCorp Terraform is primarily used to manage infrastructure. It is responsible for creating and managing infrastructure components. For example, when we initially designed the infrastructure for this project, we started by designing the VPC. We decided to use a specific region-based VPC. We specified the number of public and private subnets, as well as setting up Internet gateways and NAT gateways, all using Terraform. Once the infrastructure was set up, we deployed our resources, such as ECS containers, ECS tasks, and RDS databases, in private subnets, all properly managed by Terraform. However, we use GitHub Actions for CI/CD pipeline purposes. While Terraform handles the infrastructure management, GitHub Actions manages the CI/CD pipeline for our ECS clusters. In my previous project, we used Jenkins, but in this project, we use GitHub Actions for deployment, testing, and other pipeline tasks.
I use the solution in my company to create services over cloud platforms. I have used HashiCorp Terraform for GCP, Azure, and AWS to create resources. With HashiCorp Terraform, it is easy to manage resources in a single file.
Initially, We have started using Terraform for provision cloud infrastructure and slowly our requirement keep growing up currently my team is using Terraform for managing AWS/Azure/GCP or I should multiple clouds along with Kubernetes/Rancher, Gitlab, MySQL/Oracle, datadog.
We use Terraform for many different use cases. The primary one is ensuring that the security policy is automatically applied to all of the resources within a cloud environment. Another one would be creating and dismantling all sorts of test labs, as well as creating a development environment. We found a way to automatically create a development environment only for the time we need. We develop the infrastructure and cloud-related tasks.
My company uses HashiCorp Terraform for cloud infrastructure provisioning. HashiCorp Terraform is the only IaC tool we use in our company.
Terraform is our main infrastructure as code at the bank. Our entire deployment site and the AWS solution are based on Terraform. We use EBridge and the Dochub solution on the Bitbucket pipeline. Terraform runs on a container in the Bitbucket pipeline, but to create my entire cloud solution, I use EBridge.
Our primary use for the solution is to create infrastructure on the cloud. We are a cloud integrator. We write our codes in Terraform and reuse them for multiple customers by changing the values.
We use it to deploy resources on AWS.
We use the solution for provisioning.
We use HashiCorp Terraform orchestration tool for infra provisioning (mostly servers), both in the cloud and on-premise environments. This allows for VM provisioning, networking, and storage management, especially in a cloud environment where we have many servers that can't be provisioned one by one.
Our company uses the solution to deploy resources and infrastructure in Azure Cloud via the Azure DevOps pipelines. We have two developers who use the solution.
HashiCorp Terraform is a tool used for provisioning cloud infrastructure. It is used in this specific use case to deploy and provision all services, including Kafka, MongoDB, and Postgres clusters, using infrastructure as code.
We have about 50 users.
We use this solution to manage our resources in a fully automatic way. I'm a senior Azure DevOps engineer and we are users of Terraform.
We use HashiCorp Terraform to set up AWS infrastructure, and sometimes Cloudflare. It is not exactly a tool for configuration, it is for setting up the development of the infrastructure.
We use HashiCorp Terraform to deploy applications and infrastructures.
HashiCorp Terraform is a binary executable file, that you can download to your PC and manage any cloud solution in the world, such as Google Cloud Platform, Amazon AWS, OpenStack, CloudStack, or VMware. When you use DevOps in your company, it's a useful tool for it.
Terraform is the infrastructure as code solution used across our business.
A primary use case of Terraform is for deploying a VM on a cloud using Terraform script. If I then want to deploy a third-party toolset, a solution such as Aviatrix can create an overlay on top of each of the cloud providers and you can connect the clouds together. I'm a solutions architect and we are customers of HashiCorp.
We use this solution for infrastructure and support for a mobile application for a bank.
I use the latest version.
We are using it for infrastructure as code automation. We are running its latest version.
We are using Terraform to manage our multi-cloud requirement for different demos and test environments. It helps us set up the entire environment in a few mins with the exact configuration in AWS, Azure, or GCP, along with other setups like a database, Kubernetes, etc.
I mainly use it for infrastructure automation. I use it to provision servers in different cloud providers and in-house with the principles to create a Kubernetes cluster. If you have a master node concept I would create the master and find related text. The main function for me is to create infrastructure.
We deliver the platform as a service to businesses. For example, one request for a particular subscription could be in the business domain or non-business domain, whatever it may be, based on the demand, we deliver the customized subscription to them. For each service, we have different constraints. What needs to be delivered in the VNet of Azure, and what needs to be done externally.
We use it to provision cloud infrastructure. We use it to provision all kinds of infrastructure from wherever we want, we Terraform to the cloud. We provision new infrastructure, we update existing infrastructure with it, we manage our DNS records, and also deploy new applications on Kubernetes. That's the main use, but we use it for all of our infrastructures, so it has a lot of different use cases.