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.