Terraform state rm for removing resources - Commands & Configuration

Introduction

Sometimes Terraform's state file has resources that no longer exist or should be managed outside Terraform. The terraform state rm command removes these resources from the state without deleting the actual infrastructure.

When you manually delete a resource outside Terraform and want to update the state to match.

When you want to stop managing a resource with Terraform but keep it running.

When you imported a resource by mistake and want to remove it from state.

When cleaning up state entries for resources that no longer exist.

When splitting infrastructure management between different Terraform projects.

Commands

Initialize the Terraform working directory to download providers and set up the backend.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/aws...

- Installing hashicorp/aws v4.50.0...

- Installed hashicorp/aws v4.50.0 (signed by HashiCorp)



Terraform has been successfully initialized!



You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure.

List all resources currently tracked in the Terraform state to identify the exact resource address to remove.

Terminal

terraform state list

Expected Output

aws_instance.my_server

aws_s3_bucket.my_bucket

Remove the aws_instance.my_server resource from the Terraform state without deleting the actual AWS instance.

Terminal

terraform state rm aws_instance.my_server

Expected Output

Removed aws_instance.my_server

Verify that the resource aws_instance.my_server is no longer tracked in the Terraform state.

Terminal

terraform state list

Expected Output

aws_s3_bucket.my_bucket

Key Concept

If you remember nothing else from this pattern, remember: terraform state rm removes resources from Terraform's tracking without deleting the real infrastructure.

Common Mistakes

Running terraform destroy instead of terraform state rm to remove a resource.

terraform destroy deletes the actual resource in the cloud, which may cause unwanted downtime or data loss.

Use terraform state rm to only remove the resource from Terraform's state while keeping it running.

Removing the wrong resource address due to incorrect resource name.

Removing the wrong resource from state can cause Terraform to lose track of important infrastructure.

Always run terraform state list first to confirm the exact resource address before removing.

Summary

Run terraform init to prepare your working directory.

Use terraform state list to see all tracked resources.

Run terraform state rm with the exact resource address to remove it from state without deleting it.

Verify removal by listing state again.

Practice

1. What does the terraform state rm command do?

easy

A. Deletes the resource from the cloud provider and Terraform state

B. Removes a resource from Terraform's state without deleting the actual resource

C. Updates the resource configuration in Terraform files

D. Creates a new resource and adds it to the state

Solution

1. Step 1: Understand the purpose of terraform state rm

   This command tells Terraform to stop tracking a resource by removing it from the state file.

2. Step 2: Recognize it does not delete the actual resource

   The real resource remains intact in the cloud; only Terraform forgets it.

3. Final Answer:

   Removes a resource from Terraform's state without deleting the actual resource -> Option B

4. Quick Check:

   State removal only forgets resource [OK]

Hint: Remember: state rm forgets resource, does not delete it [OK]

Common Mistakes:

• Thinking it deletes the actual resource
• Confusing it with terraform destroy
• Assuming it updates resource configuration

2. Which of the following is the correct syntax to remove a resource named aws_instance.example from Terraform state?

easy

A. terraform rm state aws_instance.example

B. terraform remove aws_instance.example

C. terraform state rm aws_instance.example

D. terraform state delete aws_instance.example

Solution

1. Step 1: Recall the correct command structure

   The command to remove a resource from state is terraform state rm <resource_name>.

2. Step 2: Match the resource name format

   The resource name is aws_instance.example, so the full command is terraform state rm aws_instance.example.

3. Final Answer:

   terraform state rm aws_instance.example -> Option C

4. Quick Check:

   Correct command syntax [OK]

Hint: Use 'terraform state rm' followed by resource name [OK]

Common Mistakes:

• Swapping 'rm' and 'state' keywords
• Using 'remove' or 'delete' instead of 'rm'
• Incorrect command order

3. Given the following Terraform state command:

terraform state rm aws_s3_bucket.my_bucket

What will happen after running this command?

medium

A. Terraform will remove the S3 bucket from state but the bucket remains in AWS

B. Terraform will update the S3 bucket configuration in the state

C. Terraform will delete the S3 bucket from AWS and remove it from state

D. Terraform will show an error because the command is incomplete

Solution

1. Step 1: Understand the effect of terraform state rm

   This command removes the resource from Terraform's state file only.

2. Step 2: Recognize the real resource remains untouched

   The actual S3 bucket in AWS is not deleted or changed by this command.

3. Final Answer:

   Terraform will remove the S3 bucket from state but the bucket remains in AWS -> Option A

4. Quick Check:

   State removal keeps resource intact [OK]

Hint: State rm forgets resource, does not delete it in cloud [OK]

Common Mistakes:

• Assuming the resource is deleted from AWS
• Thinking the state file is updated with new config
• Believing the command is incomplete

4. You ran terraform state rm aws_instance.web but later realized you still want Terraform to manage this instance. What is the best way to fix this?

medium

A. Run terraform import aws_instance.web <instance_id> to re-add it to state

B. Run terraform state add aws_instance.web to add it back

C. Run terraform state rm aws_instance.web again to undo

D. Delete the instance manually and recreate it

Solution

1. Step 1: Understand that terraform state rm only removes from state

   Once removed, Terraform no longer tracks the resource.

2. Step 2: Use terraform import to re-add the existing resource to state

   This command links the real resource back to Terraform's state file.

3. Final Answer:

   Run terraform import aws_instance.web <instance_id> to re-add it to state -> Option A

4. Quick Check:

   Import command restores resource to state [OK]

Hint: Use terraform import to re-add removed resources [OK]

Common Mistakes:

• Trying to use a non-existent 'state add' command
• Running state rm again expecting undo
• Deleting resource unnecessarily

5. You want to stop managing a resource google_compute_instance.vm1 with Terraform but keep it running in your cloud. Which sequence of commands achieves this safely?

hard

A. Run terraform state rm google_compute_instance.vm1 then manually delete the resource

B. Run terraform destroy -target=google_compute_instance.vm1 to remove it from cloud and state

C. Remove the resource block from Terraform files and run terraform apply

D. Run terraform state rm google_compute_instance.vm1 only to remove it from state and keep it running

Solution

1. Step 1: Use terraform state rm to remove resource from state

   This stops Terraform from managing the resource but does not delete it.

2. Step 2: Avoid deleting the resource or removing config to keep it running

   Deleting or removing config and applying would delete or recreate the resource.

3. Final Answer:

   Run terraform state rm google_compute_instance.vm1 only to remove it from state and keep it running -> Option D

4. Quick Check:

   State rm forgets resource, keeps it running [OK]

Hint: State rm removes from Terraform control, resource stays alive [OK]

Common Mistakes:

• Deleting resource after state rm
• Using terraform destroy which deletes resource
• Removing config without state rm causes resource deletion