> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/infrastructure-as-code-management/new-to-iacm/get-started/terraform-get-started.md).

# Get Started With Terraform

Use this guide to create a Terraform workspace. Provision infrastructure through Harness Infrastructure as Code Management (IaCM).

### What is IaCM? <a href="#what-is-iacm-iacm-what-is-iacm" id="what-is-iacm-iacm-what-is-iacm"></a>

IaC automates infrastructure management via code. IaCM enhances this by ensuring consistent, accountable, and repeatable deployments. Harness boosts IaCM with [**real-time cost estimation**](/infrastructure-as-code-management/platform/workspaces/cost-estimation.md), [**automated policy enforcement**](/infrastructure-as-code-management/platform/policy-and-governance/terraform-plan-cost-policy.md), and [**drift detection**](/infrastructure-as-code-management/platform/iacm-pipelines/operations-overview.md), ensuring efficient provisioning and compliance with standards.

{% hint style="info" %}
**TERRAFORM TO OPENTOFU MIGRATION**

Harness IaCM supports integration with all **OpenTofu** versions.\
For **Terraform**, we support all MPL versions up to **1.5.x**, any BSL versions (from 1.6.0) are not supported.

Follow this [**OpenTofu migration guide**](https://opentofu.org/docs/intro/migration/) to transition from Terraform to OpenTofu and leverage the benefits of this open-source alternative.
{% endhint %}

Go to [What's Supported in IaCM](/infrastructure-as-code-management/troubleshooting-and-resources/whats-supported.md) for more information on supported Cloud Providers and Code/Git providers.

{% @harness-package-selector/package-selector platforms="%5B%7B%22label%22%3A%22AWS%20CDK%22%2C%22slug%22%3A%22aws-cdk%22%2C%22path%22%3A%22infrastructure-as-code-management%2Fnew-to-iacm%2Fget-started%2Faws-cdk-get-started%22%7D%2C%7B%22label%22%3A%22OpenTofu%22%2C%22slug%22%3A%22opentofu%22%2C%22path%22%3A%22infrastructure-as-code-management%2Fnew-to-iacm%2Fget-started%2Fopentofu-get-started%22%7D%2C%7B%22label%22%3A%22Terragrunt%22%2C%22slug%22%3A%22terragrunt%22%2C%22path%22%3A%22infrastructure-as-code-management%2Fnew-to-iacm%2Fget-started%2Fterragrunt-get-started%22%7D%2C%7B%22label%22%3A%22Terraform%22%2C%22slug%22%3A%22terraform%22%2C%22path%22%3A%22infrastructure-as-code-management%2Fnew-to-iacm%2Fget-started%2Fterraform-get-started%22%7D%5D" selectedPlatform="terraform" %}

Terraform is a widely used infrastructure-as-code tool. Harness Infrastructure as Code Management (IaCM) runs MPL-licensed Terraform versions in workspaces and pipelines, with Git-backed configuration, connectors, and optional cost estimation.

This guide walks you from connectors and workspace creation through a standard provision pipeline (init, plan, apply) and an optional approval between plan and apply.

### What you will learn from this topic <a href="#what-will-you-learn" id="what-will-you-learn"></a>

This guide covers the following:

* **Connectors and workspace:** Create cloud and Git connectors, then create a Terraform workspace wired to your repository and Terraform version.
* **Provision pipeline:** Generate or author a pipeline that runs init, plan, and apply for your workspace.
* **Approvals:** Optionally gate apply behind an approval step.

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

Before you use this guide, ensure you have the following:

* **Harness account with IaCM enabled:** You need **Infrastructure as Code Management** under **Infrastructure** in Harness when it is entitled on your account. Go to [Getting started with Harness Platform](/harness-ai/new-to-harness-platform/get-started.md) to access or create a Harness account.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>CONTACT HARNESS SUPPORT</strong></p><p>If IaCM does not appear, go to <a href="/pages/13Oqw5qhSvsXSpzVztiw">Get started with IaCM</a>, or contact your account administrator or <a href="mailto:support@harness.io">Harness Support</a>.</p></div>
* **Pipeline permissions:** View, Create/Edit, and Execute on [Pipelines](/harness-ai/use-harness-platform/platform-access-control/permissions-reference.md#pipelines). Go to [RBAC in Harness](/harness-ai/use-harness-platform/platform-access-control.md) to review the permissions model, and go to [Manage roles](/harness-ai/use-harness-platform/platform-access-control/add-manage-roles.md) to assign a role that includes them.
* **Git repository:** Access to a Git provider with your Terraform project.
* **Cloud provider:** Access to a cloud provider such as AWS or Google Cloud Platform for the infrastructure you manage.
* **Harness organization and project:** An [organization and project set up](/harness-ai/new-to-harness-platform/get-started.md) on the Harness Platform.

<details>

<summary>Sample Terraform</summary>

The following example Terraform (.tf) file declares:

* **Provider Configuration:** Specifies the AWS provider and sets the region to "us-east-1". Go to [AWS Regions & Availability Zones](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html) for a complete region list.
* **Resource Definition:** Creates an EC2 instance with the identifier `my_first_ec2_instance`.
* **AMI:** Utilizes ami-123abc321cba18, go to [AWS EC2 User Guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/finding-an-ami.html) to find your AMI image ID.
* **Instance Type:** Configures the instance to use a t2.micro. Go to the [AWS t2 instances list](https://aws.amazon.com/ec2/instance-types/t2/).\
  Tags: To facilitate easy identification and management within AWS resources, a tag name with the value `my_first_ec2_instance` is applied.

```hcl
provider "aws" {
  region = "us-east-1"
}

resource "aws_instance" "my_first_ec2_instance" {
  ami = "ami-123abc321cba18"
  instance_type = "t2.micro" # Go to https://aws.amazon.com/ec2/instance-types/t2/ for a full T2 instance type list.

  tags = {
    Name = "my_first_ec2_instance"
  }
}
```

Go to [Terraform Documentation](https://developer.hashicorp.com/terraform/docs) to review currently supported workspace types.

</details>

***

### Set up your workspace <a href="#set-up-your-workspace" id="set-up-your-workspace"></a>

A workspace is a named environment for storing your Terraform configurations and resources. Connect your Cloud Provider and Code Repository through **Connectors** to manage infrastructure changes and updates with Harness IaCM pipelines.

{% hint style="info" %}
Harness recommends configuring your connector before creating your workspace, however, you can also add new connectors during the [Create Workspace flow](/infrastructure-as-code-management/new-to-iacm/get-started.md#add-a-new-workspace).
{% endhint %}

#### Step 1: add connectors <a href="#step-1-add-connectors" id="step-1-add-connectors"></a>

Use **Harness AI** to create and configure your cloud provider and code repository connectors before you create a workspace:

{% tabs %}
{% tab title="Create a Connector" %}
{% embed url="<https://app.tango.us/app/embed/73d9628e-7093-4c6b-a9f7-dac8125c8441?skipCover=true&defaultListView=false&skipBranding=false&makeViewOnly=true&hideAuthorAndDetails=true>" %}
Create Cloud Provider Connector with Harness AI
{% endembed %}
{% endtab %}

{% tab title="Step-by-step" %}
When adding any connector, start by:

1. Sign in to [app.harness.io](https://app.harness.io).
2. In the module pane, select **Infrastructure**.
3. Select **Project Setup**, and then select **Connectors**.
4. Select **New Connector (AI)**.
5. Select an option, for example "Create a GitHub connector", or type your request to create a connector for your chosen cloud provider or code repository.

Harness creates a YAML file for your connector. Once you select **Create**, Harness creates your connector and adds it to your project.

{% hint style="info" %}
**EDIT CONNECTOR**

Edit your connector by updating the AI generated YAML file, or by selecting **Edit Details** in the connectors panel.
{% endhint %}

Go to [Connect your Cloud Provider](/harness-ai/use-harness-platform/connectors/cloud-providers.md) and [Connect your Code Repository](/harness-ai/use-harness-platform/connectors/code-repositories/connect-to-code-repo.md) to connect your cloud provider and code repository.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**OIDC CONNECTORS**

For easier access and token management, use the **OIDC** (OpenID Connect) option in the Credentials panel. This allows your connector to assume roles with permissions set in your Cloud Provider, updated only by authorized users. Go to [the Use OIDC tab](/harness-ai/use-harness-platform/connectors/cloud-providers/ref-cloud-providers/aws-connector-settings-reference.md#credentials) for setup details.
{% endhint %}

***

#### Step 2: create your workspace <a href="#step-2-create-your-workspace" id="step-2-create-your-workspace"></a>

Once you have configured your connectors, you can create a workspace and select them in the **New Workspace** panel:

{% hint style="info" %}
**MIGRATE EXISTING PROJECTS**

For first-time use, go to [State Migration](/infrastructure-as-code-management/use-iacm/remote-backends/state-migration.md) to import the state of your existing Terraform projects into a Harness workspace.
{% endhint %}

{% tabs %}
{% tab title="Interactive Guide" %}
{% embed url="<https://app.tango.us/app/embed/2b521884-bbdd-4764-9673-3bbd0529a8a0?skipCover=true&defaultListView=false&skipBranding=false&makeViewOnly=true&hideAuthorAndDetails=true>" %}
Create a Terraform Workspace in Harness IaCM
{% endembed %}
{% endtab %}

{% tab title="Step-by-step" %}

1. In the module pane, select **Infrastructure**.
2. Select an existing project or create a new project.
3. Select **Workspaces**, and then select **New Workspace**.
4. Select **Create new Workspace**, then select **Start from scratch** and complete the following fields in the new workspace wizard:

**About workspace**

* **Name** - Enter a unique name to identify the workspace.
* **Description (optional)**: Enter an optional description to help identify the workspace.
* **Tags (optional)**: Add a unique tag to identify the workspace.

**Configure repository details**

* Select your Git provider, either **Harness Code Repository** or **Third-party Git provider** for other providers like GitHub or GitLab.
* **Git Connector**: Select the Git connector you created in the previous step.
* **Git Fetch Type**: Select the Git fetch type, either **Latest from branch**, **Git tag** or **Commit SHA**.
* **Git Branch**: Specify the branch you want to use for the workspace.

{% hint style="info" %}
**BRANCH WITH JEXL**

You can configure the workspace branch as a [JEXL expression](/harness-ai/use-harness-platform/variables-and-expressions/harness-variables.md) that references a pipeline variable, and then set the pipeline variable as a runtime input.

<img src="/files/nK2EEySgnYT2v80XVEot" alt="" data-size="original">

Set your branch variable as a runtime input in the pipeline:

```yaml
variables:
 - name: iacm_branch
   type: String
   description: ""
   required: true
   value: <+input>.default(main)
```

{% endhint %}

* **Folder Path**: Specify the folder path to the Terraform configuration files in the repository.

**Advanced** options allow you to **include submodules** if your code repository includes modules and submodules. Go to [Module Registry](/infrastructure-as-code-management/registry/module-registry.md) to review module registry concepts.

**Provisioner**

* **Connector**: Select the cloud provider connector you created in the previous step.
* **Cloud Cost Estimation**: Toggle the **Enable Cost Estimation** switch to enable cloud cost estimation. This lets you estimate the cost of your infrastructure changes before you apply them.
* **Workspace Type**: Select **Terraform** as the workspace type you want to use for the workspace.
* **Terraform Version**: Select the Terraform version you want to use for the workspace, up to version 1.5.x (MPL licenses).

**Add variable set (optional)**

If you have configured variable sets for reuse, select the variable set you want to use for the workspace.

5. Select **Create**.
   {% endtab %}
   {% endtabs %}

***

#### Step 3: add a provision pipeline <a href="#step-3-add-a-provision-pipeline" id="step-3-add-a-provision-pipeline"></a>

A pipeline structures workflows to manage tasks like planning infrastructure changes, enforcing policies, and approvals. Go to [Harness Pipelines](/harness-ai/use-harness-platform/pipelines.md) to review pipeline concepts. You can also add pipelines through the Harness Platform or [use a code-first approach with YAML](/harness-ai/use-harness-platform/pipelines/create-pipeline-quickstart.md).

**Harness AI pipeline generation**

{% tabs %}
{% tab title="Interactive Guide" %}
{% embed url="<https://app.tango.us/app/embed/067e325b-9f3b-46e7-8ff2-5b671ea13276?skipCover=true&defaultListView=false&skipBranding=false&makeViewOnly=true&hideAuthorAndDetails=true>" %}
Create a provision pipeline in Harness IaCM for Terraform
{% endembed %}
{% endtab %}

{% tab title="Step-by-step" %}
Start by adding the pipeline:

1. Select the **Infrastructure** module.
2. Select **Pipelines**, then select **Create a Pipeline**.
3. Select an option from Harness AI chat or type a request to generate one, for example:
   * "Create a pipeline to Provision a Terraform files with an init, plan and apply step."
4. Review the generated YAML and Harness AI chat summary, and make any changes if necessary.
5. Select **Accept**.
   {% endtab %}
   {% endtabs %}

The Provision operation adds three Terraform plugin steps: `init`, `plan`, and `apply`. Go to [Tofu/Terraform Plugins](/infrastructure-as-code-management/use-iacm/iacm-cli-commands/terraform-plugins.md) to review supported OpenTofu/Terraform commands.

***

#### Step 4: add an approval step (optional) <a href="#step-4-add-an-approval-step-optional" id="step-4-add-an-approval-step-optional"></a>

You can add the Approval step to prompt a review of the previous pipeline stage before proceeding. The most common use case is to add the Approval step between the `plan` and `apply` steps so you can review infrastructure changes and estimated costs (if cost estimation is enabled on your workspace) before applying them.

{% hint style="warning" %}
**APPROVAL STEPS HOLD RESOURCES**

When using an Approval step, the underlying machine running the pipeline remains active until the approval is resolved. This means it will continue consuming compute resources.
{% endhint %}

{% tabs %}
{% tab title="Interactive Guide" %}
{% embed url="<https://app.tango.us/app/embed/067e325b-9f3b-46e7-8ff2-5b671ea13276?skipCover=true&defaultListView=false&skipBranding=false&makeViewOnly=true&hideAuthorAndDetails=true>" %}
Create a provision pipeline in Harness IaCM for Terraform
{% endembed %}
{% endtab %}

{% tab title="Step-by-step" %}

1. From the Pipeline > **Execution** tab, click the **Add** icon between `plan` and `apply`.

![Add Approval Step](/files/uJoew1V93ZrDlujcHMvP)

2. Click **Add Step**.
3. Under **IACM**, select **IACM Approval**.
4. Name the approval step and click **Apply Changes**.
5. Click **Save**, then click **Run** to run your pipeline.
   {% endtab %}
   {% endtabs %}

### Next steps <a href="#next-steps-iacm-next-steps" id="next-steps-iacm-next-steps"></a>

This guide introduced you to the core functionalities and setup of Harness IaCM, from creating workspaces to configuring pipelines. To enhance your experience and team efficiency, get the most out of Harness IaCM's built-in reusable features, including:

* [**Workspace Templates:**](/infrastructure-as-code-management/platform/workspaces/workspace-templates.md) Quickly create new workspaces using pre-defined, customizable templates.
* [**Module Registry:**](/infrastructure-as-code-management/registry/module-registry.md) Share and reuse infrastructure modules across teams to standardize deployments.
* [**Default Pipelines:**](/infrastructure-as-code-management/platform/iacm-pipelines/default-pipelines.md) Start with ready-made pipeline templates to accelerate automation and best practices.
* [**Queue Step:**](/infrastructure-as-code-management/platform/iacm-pipelines/operations-overview.md) Serialize your pipeline execution to track concurrent executions and prevent state conflicts.
* [**Harness CLI:**](/infrastructure-as-code-management/use-iacm/iacm-cli-commands/harness-cli.md) Install the unified CLI to list, get, and execute IaCM workspaces from your terminal.

Go to [Harness AI Chat use cases](/harness-ai/untitled-1/use-harness-ai/use-cases/harness-ai-chat-guide.md) for more use cases on Harness AI, and platform integration.

For an interactive onboarding experience including further use cases and features like \*\*drift detection\*\*, \*\*remote backends\*\*, and \*\*policy enforcement\*\*, check out \[\*\*Harness IaCM self-paced training\*\*]\(<https://university-registration.harness.io/self-paced-training-harness-infrastructure-as-code-management>).