Import limitations and considerations in Terraform - Commands & Configuration

Introduction

Sometimes you have existing cloud resources that you want to manage with Terraform. Importing lets Terraform track these resources. But there are limits and things to watch out for to avoid problems.

When you have a cloud server already running and want Terraform to manage it without recreating it

When you want to bring existing storage buckets under Terraform control

When you need to manage resources created manually or by other tools

When migrating infrastructure management to Terraform without downtime

When you want to avoid deleting and recreating resources during Terraform setup

Commands

This command imports an existing AWS EC2 instance with ID i-0abcd1234efgh5678 into Terraform state under the resource name aws_instance.my_server. It lets Terraform track this instance without changing it.

Terminal

terraform import aws_instance.my_server i-0abcd1234efgh5678

Expected Output

aws_instance.my_server: Importing from ID "i-0abcd1234efgh5678"...

aws_instance.my_server: Import prepared!

  Prepared aws_instance for import

aws_instance.my_server: Refreshing state... [id=i-0abcd1234efgh5678]



Import successful!



The resources that were imported are now in your Terraform state and will be managed by Terraform.

This command shows what Terraform will do next. After import, it helps verify if the imported resource matches your Terraform configuration or if changes will be applied.

Terminal

terraform plan

Expected Output

No changes. Infrastructure is up-to-date.

Key Concept

If you remember nothing else from this pattern, remember: Terraform import only adds existing resources to state; it does not create configuration or change resources automatically.

Common Mistakes

Running terraform import without having the matching resource block in the configuration file

Terraform imports the resource into state but cannot manage it properly without the configuration, leading to errors or confusion.

Always write the resource block in your Terraform files before importing the resource.

Expecting terraform import to create or modify resources

Import only adds existing resources to Terraform state; it does not create or change resources.

Use terraform import only for existing resources; use terraform apply to create or modify.

Not verifying the imported resource with terraform plan after import

The imported resource may differ from the configuration, causing unexpected changes on apply.

Always run terraform plan after import to check for differences.

Summary

Use terraform import to add existing resources to Terraform state without recreating them.

Always have the matching resource configuration in your Terraform files before importing.

Run terraform plan after import to verify the imported resource matches your configuration.

Practice

1. What is the main purpose of the terraform import command?

easy

A. To delete resources from the cloud provider

B. To create new resources from scratch

C. To bring existing resources under Terraform management without recreating them

D. To update Terraform itself to the latest version

Solution

1. Step 1: Understand the role of terraform import

   The terraform import command is used to take resources that already exist outside Terraform and bring them into Terraform's control without deleting or recreating them.

2. Step 2: Differentiate from other commands

   Creating new resources is done with terraform apply, deleting is done with terraform destroy, and updating Terraform is unrelated to resource import.

3. Final Answer:

   To bring existing resources under Terraform management without recreating them -> Option C

4. Quick Check:

   terraform import = bring existing resources under control [OK]

Hint: Import means adopt existing resources, not create new ones [OK]

Common Mistakes:

• Thinking import creates new resources
• Confusing import with resource deletion
• Assuming import updates Terraform version

2. Which of the following is required before running terraform import for a resource?

easy

A. The resource must be deleted first

B. The resource must be created by Terraform previously

C. Terraform must be initialized with terraform init after import

D. The resource configuration must exist in the Terraform files

Solution

1. Step 1: Check Terraform import requirements

   Before importing, Terraform needs a matching resource block in the configuration files to map the imported resource to.

2. Step 2: Understand other options

   The resource should not be deleted before import; terraform init is run before import, not after; and the resource does not need to be created by Terraform previously.

3. Final Answer:

   The resource configuration must exist in the Terraform files -> Option D

4. Quick Check:

   Config must exist before import [OK]

Hint: Write resource config first, then import [OK]

Common Mistakes:

• Trying to import without resource config
• Deleting resource before import
• Running terraform init after import

3. Given this Terraform resource configuration:

resource "aws_s3_bucket" "mybucket" {
  bucket = "my-existing-bucket"
}

What happens if you run terraform import aws_s3_bucket.mybucket my-existing-bucket?

medium

A. Terraform imports the existing S3 bucket and manages it without changes

B. Terraform deletes the existing bucket and creates a new one

C. Terraform throws an error because the bucket name is missing

D. Terraform creates a duplicate bucket with a different name

Solution

1. Step 1: Match resource config and import command

   The resource block matches the bucket name used in the import command, so Terraform will link the existing bucket to this resource.

2. Step 2: Understand import behavior

   Import does not delete or recreate resources; it only brings them under Terraform management.

3. Final Answer:

   Terraform imports the existing S3 bucket and manages it without changes -> Option A

4. Quick Check:

   Import links existing resource without changes [OK]

Hint: Import links existing resource, no deletion [OK]

Common Mistakes:

• Assuming import deletes or recreates resource
• Confusing import with apply
• Using wrong resource ID format

4. You run terraform import aws_instance.web i-1234567890abcdef0 but get an error saying the resource ID format is invalid. What is the most likely cause?

medium

A. Terraform was not initialized with terraform init

B. The resource ID does not match the expected format for the AWS provider

C. The resource configuration block is missing in Terraform files

D. The AWS instance does not exist in the cloud

Solution

1. Step 1: Check resource ID format

   Terraform import requires the resource ID to match the provider's expected format exactly. An invalid format causes errors.

2. Step 2: Differentiate from other causes

   Missing config causes different errors; uninitialized Terraform causes different errors; non-existent resource causes not found errors, not format errors.

3. Final Answer:

   The resource ID does not match the expected format for the AWS provider -> Option B

4. Quick Check:

   Invalid ID format causes import error [OK]

Hint: Check provider docs for correct ID format before import [OK]

Common Mistakes:

• Ignoring ID format requirements
• Assuming missing config causes format error
• Skipping terraform init before import

5. You want to import multiple existing resources of the same type but with different IDs into Terraform. Which approach best handles this scenario?

hard

A. Write separate resource blocks with unique names and import each resource individually

B. Write one resource block and import all IDs at once using a comma-separated list

C. Use a single resource block with a list of IDs and import once

D. Import resources without any configuration blocks and Terraform will auto-discover them

Solution

1. Step 1: Understand Terraform resource uniqueness

   Each resource block must have a unique name to represent a single resource instance in Terraform.

2. Step 2: Import multiple resources properly

   To import multiple resources, create multiple resource blocks with unique names and import each resource ID separately.

3. Step 3: Eliminate incorrect options

   Terraform does not support importing multiple IDs at once in one resource block or auto-discovery without config.

4. Final Answer:

   Write separate resource blocks with unique names and import each resource individually -> Option A

5. Quick Check:

   One resource block per resource, import individually [OK]

Hint: One resource block per resource, import separately [OK]

Common Mistakes:

• Trying to import multiple IDs in one resource block
• Assuming Terraform auto-discovers resources
• Using comma-separated IDs in import command