Import limitations and considerations in Terraform - Step-by-Step Execution

Process Flow - Import limitations and considerations

Start Import Command

↓

Check Resource Exists?

No→Error: Cannot Import

Yes↓

Check Resource Supported for Import?

No→Error: Unsupported Resource

Yes↓

Check Resource State Dependencies

↓

Import Resource State into Terraform

↓

Update Terraform State File

↓

Verify Imported Resource Configuration

↓

End Import Process

This flow shows the steps Terraform follows when importing a resource, including checks for existence, support, dependencies, and updating state.

Execution Sample

Terraform

terraform import aws_instance.example i-1234567890abcdef0

Imports an existing AWS EC2 instance into Terraform state under the resource name aws_instance.example.

Process Table

Step	Action	Check/Evaluation	Result/Outcome
1	Run import command	Command syntax valid?	Yes, proceed
2	Check if resource exists in provider	Does instance i-1234567890abcdef0 exist?	Yes, found
3	Check if resource type supports import	Is aws_instance import supported?	Yes, supported
4	Check resource dependencies	Are dependencies manageable?	Yes, no blocking dependencies
5	Import resource state	Fetch resource attributes	Attributes fetched successfully
6	Update Terraform state file	State file updated with resource	Success
7	Verify imported resource configuration	Does config match imported state?	Partial match, manual config update may be needed
8	End import process	Import complete	Resource now managed by Terraform

💡 Import ends after resource state is fetched and Terraform state file is updated.

Status Tracker

Variable	Start	After Step 2	After Step 5	Final
resource_exists	unknown	true	true	true
import_supported	unknown	unknown	true	true
resource_state	empty	empty	populated	populated
terraform_state_file	unchanged	unchanged	updated	updated

Key Moments - 3 Insights

Why does Terraform fail if the resource does not exist in the provider during import?

Terraform needs to find the actual resource to import its state. If it doesn't exist (see Step 2 in execution_table), import cannot proceed.

What happens if the resource type does not support import?

Terraform cannot import unsupported resource types (Step 3). You must manage those resources manually or recreate them in Terraform.

Why might the imported resource configuration not fully match the Terraform config?

Import only brings state, not config code. Manual updates to Terraform files may be needed to reflect actual resource settings (Step 7).

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Terraform confirm the resource exists?

A Step 2

B Step 1

C Step 4

D Step 6

💡 Hint

Check the 'Check if resource exists in provider' action in execution_table row 2.

According to variable_tracker, when does terraform_state_file get updated?

A After Step 2

B After Step 5

C Final

D Start

💡 Hint

Look at terraform_state_file variable changes in variable_tracker after Step 5.

If the resource is not supported for import, what is the expected outcome in the flow?

A Import proceeds normally

B Resource state is partially imported

C Error: Unsupported Resource

D Terraform automatically creates the resource

💡 Hint

Refer to concept_flow where unsupported resource leads to error.

Concept Snapshot

terraform import <resource_type>.<name> <id>
- Imports existing resource state into Terraform
- Resource must exist and support import
- Updates Terraform state file only
- Manual config update may be needed
- Errors if resource missing or unsupported

Full Transcript

Terraform import lets you bring existing cloud resources under Terraform management by importing their state. The process starts by running the import command with resource type, name, and ID. Terraform checks if the resource exists in the cloud provider. If it does not, import fails. Next, Terraform verifies if the resource type supports import. Unsupported types cause an error. Then Terraform checks dependencies to ensure import can proceed. It fetches the resource attributes and updates the Terraform state file. Finally, you should verify and update your Terraform configuration files to match the imported resource. This process helps avoid recreating resources and keeps Terraform state accurate.

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