Terraform Cloud overview - Step-by-Step Execution

Process Flow - Terraform Cloud overview

Write Terraform Code

↓

Push Code to VCS

↓

Terraform Cloud Detects Change

↓

Terraform Cloud Runs Plan

↓

Review Plan in UI

↓

Approve Apply

↓

Terraform Cloud Applies Changes

↓

State Stored Securely in Cloud

↓

Outputs and Logs Available

↓

End

This flow shows how Terraform Cloud automates infrastructure deployment by detecting code changes, running plans, applying changes, and storing state securely.

Execution Sample

Terraform

terraform {
  cloud {
    organization = "my-org"
    workspaces {
      name = "my-workspace"
    }
  }
}

This Terraform block configures Terraform Cloud to use a specific organization and workspace for managing infrastructure.

Process Table

Step	Action	Result	Next Step
1	Write Terraform code locally	Code ready for deployment	Push code to version control system
2	Push code to GitHub	Terraform Cloud detects new commit	Start Terraform plan
3	Terraform Cloud runs plan	Shows proposed infrastructure changes	User reviews plan in UI
4	User approves apply	Terraform Cloud applies changes	Update infrastructure and state
5	Terraform Cloud updates state	State stored securely in cloud	Outputs and logs available
6	User views outputs and logs	Confirms infrastructure status	End process

💡 Process ends after infrastructure is updated and state is stored securely.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
Terraform Code	Empty	Committed to VCS	Planned and approved	Deployed via Terraform Cloud
Terraform State	None	None	Being updated	Stored securely in Terraform Cloud
Infrastructure	Not created	Not created	Applying changes	Created/Updated

Key Moments - 3 Insights

Why does Terraform Cloud run a plan before applying changes?

Terraform Cloud runs a plan to show what changes will happen before making them. This helps avoid surprises and lets users review changes safely, as seen in step 3 of the execution_table.

Where is the Terraform state stored when using Terraform Cloud?

The state is stored securely in Terraform Cloud, not locally. This is shown in step 5 where the state is updated and saved in the cloud.

What triggers Terraform Cloud to start a plan?

Pushing code changes to the connected version control system triggers Terraform Cloud to detect the change and start a plan automatically, as shown in step 2.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 3?

A Terraform Cloud runs a plan showing proposed changes

B User approves the apply

C Terraform Cloud stores state securely

D Code is pushed to version control

💡 Hint

Check the 'Action' and 'Result' columns for step 3 in the execution_table.

At which step is the Terraform state updated and stored securely?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Look for the step mentioning 'Terraform Cloud updates state' in the execution_table.

If the user does not approve the apply, what happens next?

A Terraform Cloud applies changes anyway

B Terraform Cloud deletes the workspace

C The process stops before applying changes

D Terraform Cloud automatically approves the apply

💡 Hint

Refer to step 4 where user approval is required before applying changes.

Concept Snapshot

Terraform Cloud automates infrastructure deployment.
Push code to version control triggers Terraform Cloud.
It runs a plan to show changes.
User reviews and approves apply.
Terraform Cloud applies changes and stores state securely.
Outputs and logs are available for review.

Full Transcript

Terraform Cloud is a service that helps manage infrastructure by automating the deployment process. You write your Terraform code locally and push it to a version control system like GitHub. Terraform Cloud detects this change and runs a plan to show what infrastructure changes will happen. You review this plan in the Terraform Cloud user interface. Once you approve, Terraform Cloud applies the changes to your infrastructure and securely stores the state file in the cloud. You can then view outputs and logs to confirm the deployment status. This process helps keep your infrastructure consistent and safe.

Practice

1. What is the main purpose of Terraform Cloud?

easy

A. To host websites built with Terraform

B. To replace Terraform CLI on your local machine

C. To store Terraform state remotely and run Terraform commands safely

D. To provide a graphical interface for writing Terraform code

Solution

1. Step 1: Understand Terraform Cloud's role

   Terraform Cloud stores state files remotely and runs Terraform commands in a managed environment.

2. Step 2: Compare options with this role

   Only To store Terraform state remotely and run Terraform commands safely correctly describes this purpose; others describe unrelated functions.

3. Final Answer:

   To store Terraform state remotely and run Terraform commands safely -> Option C

4. Quick Check:

   Terraform Cloud = Remote state + safe runs [OK]

Hint: Remember Terraform Cloud manages state and runs commands remotely [OK]

Common Mistakes:

• Thinking Terraform Cloud replaces local CLI
• Confusing Terraform Cloud with a code editor
• Assuming Terraform Cloud hosts websites

2. Which Terraform configuration block connects your code to Terraform Cloud?

easy

A. terraform { backend "cloud" { ... } }

B. terraform { cloud { organization = "org" } }

C. provider "cloud" { organization = "org" }

D. resource "cloud" { organization = "org" }

Solution

1. Step 1: Identify the correct block for Terraform Cloud

   The terraform { cloud { ... } } block is used to configure Terraform Cloud settings.

2. Step 2: Check other options for correctness

   terraform { backend "cloud" { ... } } uses backend "cloud" which is invalid; provider and resource blocks are unrelated.

3. Final Answer:

   terraform { cloud { organization = "org" } } -> Option B

4. Quick Check:

   Cloud config = terraform block with cloud [OK]

Hint: Look for terraform { cloud { ... } } syntax [OK]

Common Mistakes:

• Using backend "cloud" instead of cloud block
• Confusing provider or resource blocks with cloud config
• Missing the organization attribute inside cloud block

3. Given this Terraform snippet, what happens when you run terraform apply?

terraform {
  cloud {
    organization = "my-org"
    workspaces {
      name = "my-workspace"
    }
  }
}

medium

A. Terraform ignores the cloud block and runs with default settings

B. Terraform runs locally and stores state on your machine

C. Terraform throws a syntax error due to missing backend block

D. Terraform connects to Terraform Cloud and uses the specified workspace

Solution

1. Step 1: Analyze the cloud block configuration

   The cloud block specifies organization and workspace, so Terraform connects to Terraform Cloud.

2. Step 2: Understand Terraform apply behavior with cloud config

   Terraform runs remotely using the workspace and stores state in Terraform Cloud.

3. Final Answer:

   Terraform connects to Terraform Cloud and uses the specified workspace -> Option D

4. Quick Check:

   Cloud block present = remote run in workspace [OK]

Hint: Presence of cloud block means remote run in Terraform Cloud [OK]

Common Mistakes:

• Assuming local run despite cloud block
• Expecting syntax error without backend block
• Ignoring workspace setting in cloud block

4. You added this block to your Terraform config but get an error:

terraform {
  cloud {
    organization = "my-org"
  }
}

What is the likely cause?

medium

A. Missing workspace configuration inside the cloud block

B. Incorrect organization name format

C. Terraform Cloud requires a backend block instead

D. The cloud block must be inside a provider block

Solution

1. Step 1: Check required fields in cloud block

   Terraform Cloud requires workspace info inside the cloud block to know where to store state.

2. Step 2: Identify missing workspace causes error

   Without workspace, Terraform cannot connect properly, causing an error.

3. Final Answer:

   Missing workspace configuration inside the cloud block -> Option A

4. Quick Check:

   Cloud block needs workspace info [OK]

Hint: Always include workspace inside cloud block [OK]

Common Mistakes:

• Assuming organization name format is wrong
• Thinking backend block is mandatory with cloud block
• Placing cloud block inside provider block

5. You want to share Terraform state safely among your team using Terraform Cloud. Which steps should you take to set this up correctly?

hard

A. Configure terraform { cloud { organization = "org" workspaces { name = "ws" } } } and push code to VCS connected to Terraform Cloud

B. Run Terraform locally and manually upload state files to Terraform Cloud

C. Use a local backend and share the state file via email with your team

D. Configure a provider block for Terraform Cloud and run terraform init locally

Solution

1. Step 1: Set up Terraform Cloud connection in config

   Use the terraform { cloud { ... } } block with organization and workspace to connect to Terraform Cloud.

2. Step 2: Integrate with version control system (VCS)

   Push your Terraform code to a VCS repository linked to Terraform Cloud for automated runs and shared state.

3. Final Answer:

   Configure terraform { cloud { organization = "org" workspaces { name = "ws" } } } and push code to VCS connected to Terraform Cloud -> Option A

4. Quick Check:

   Cloud block + VCS = safe shared state [OK]

Hint: Use cloud block and VCS integration for team state sharing [OK]

Common Mistakes:

• Uploading state files manually instead of using Terraform Cloud
• Sharing state files via email (unsafe and error-prone)
• Misusing provider block for Terraform Cloud connection