Import state verification in Terraform - Time & Space Complexity

Time Complexity: Import state verification

O(n)

Understanding Time Complexity

When Terraform imports resources, it checks the current state to match real infrastructure.

We want to know how the time needed grows as we import more resources.

Scenario Under Consideration

Analyze the time complexity of the following import verification steps.

resource "aws_instance" "example" {
  # resource config
}

terraform import aws_instance.example i-1234567890abcdef0

terraform state show aws_instance.example

This sequence imports a resource and verifies its state matches the real instance.

Identify Repeating Operations

Look at what happens repeatedly when importing multiple resources.

• Primary operation: API call to fetch resource details for each import
• How many times: Once per resource imported

How Execution Grows With Input

Each resource import triggers one API call to verify state.

Input Size (n)	Approx. API Calls/Operations
10	10 API calls
100	100 API calls
1000	1000 API calls

Pattern observation: The number of API calls grows directly with the number of resources.

Final Time Complexity

Time Complexity: O(n)

This means the time to verify state grows in a straight line as you add more resources.

Common Mistake

[X] Wrong: "Importing many resources only takes a fixed amount of time regardless of count."

[OK] Correct: Each resource needs a separate check, so time grows with how many you import.

Interview Connect

Understanding how operations scale helps you plan and explain infrastructure changes clearly.

Self-Check

"What if Terraform cached resource states locally? How would that affect the time complexity of import verification?"

Practice

1. What is the main purpose of terraform import in Terraform?

easy

A. To create new resources in the cloud

B. To update Terraform version

C. To delete resources from the cloud

D. To bring existing cloud resources into Terraform state management

Solution

1. Step 1: Understand Terraform state

   Terraform state tracks resources it manages. Existing resources outside Terraform are unknown to it.

2. Step 2: Role of terraform import

   The terraform import command adds existing resources to Terraform state without creating or deleting them.

3. Final Answer:

   To bring existing cloud resources into Terraform state management -> Option D

4. Quick Check:

   Import = Add existing resource to state [OK]

Hint: Import links existing resources to Terraform state [OK]

Common Mistakes:

• Thinking import creates new resources
• Confusing import with terraform apply
• Assuming import deletes resources

2. Which of the following is the correct syntax to import an AWS EC2 instance with ID i-1234567890abcdef0 into Terraform resource aws_instance.example?

easy

A. terraform import aws_instance i-1234567890abcdef0.example

B. terraform import aws_instance.example i-1234567890abcdef0

C. terraform import i-1234567890abcdef0 aws_instance.example

D. terraform import example.aws_instance i-1234567890abcdef0

Solution

1. Step 1: Identify correct command order

   The syntax is terraform import <resource_address> <resource_id>.

2. Step 2: Match resource address and ID

   Resource address is aws_instance.example, ID is i-1234567890abcdef0. So terraform import aws_instance.example i-1234567890abcdef0 matches syntax correctly.

3. Final Answer:

   terraform import aws_instance.example i-1234567890abcdef0 -> Option B

4. Quick Check:

   Import syntax = terraform import resource_address resource_id [OK]

Hint: Resource address first, then resource ID in import command [OK]

Common Mistakes:

• Swapping resource address and ID
• Using dot in wrong place
• Missing resource type or name

3. After running terraform import aws_s3_bucket.mybucket my-bucket-name, what will terraform plan show if the Terraform configuration matches the imported bucket exactly?

medium

A. Plan to delete the imported bucket.

B. Plan to create a new S3 bucket.

C. No changes. Terraform state matches configuration.

D. Error: Resource not found.

Solution

1. Step 1: Understand import effect

   Import adds existing resource to state but does not change configuration files.

2. Step 2: Compare state and config

   If configuration matches the imported resource exactly, terraform plan shows no changes needed.

3. Final Answer:

   No changes. Terraform state matches configuration. -> Option C

4. Quick Check:

   Matching config and state = no changes [OK]

Hint: Plan shows no changes if config matches imported state [OK]

Common Mistakes:

• Expecting terraform plan to create or delete after import
• Confusing import with apply
• Ignoring configuration mismatch

4. You ran terraform import aws_db_instance.db1 db-1234 but terraform plan shows the instance will be destroyed and recreated. What is the most likely cause?

medium

A. The Terraform configuration does not match the imported resource attributes

B. The import command was run with wrong resource ID

C. Terraform state file is corrupted

D. Terraform version is outdated

Solution

1. Step 1: Analyze import and plan mismatch

   If plan wants to destroy and recreate, it means config differs from imported resource state.

2. Step 2: Confirm configuration matches resource

   Mismatch in attributes causes Terraform to think resource needs replacement.

3. Final Answer:

   The Terraform configuration does not match the imported resource attributes -> Option A

4. Quick Check:

   Config mismatch causes resource replacement plan [OK]

Hint: Mismatch between config and imported resource causes replacement plan [OK]

Common Mistakes:

• Assuming import ID error always causes plan changes
• Blaming Terraform version without checking config
• Ignoring attribute differences

5. You want to import multiple existing AWS security groups into Terraform. Which approach ensures correct import and verification?

hard

A. Run terraform import for each security group, then run terraform plan to verify state matches configuration

B. Run terraform apply directly to create new security groups

C. Delete existing security groups and recreate with Terraform

D. Edit the Terraform state file manually to add security groups

Solution

1. Step 1: Import each existing security group

   Use terraform import with correct resource address and IDs for each group.

2. Step 2: Verify with terraform plan

   Run terraform plan to check if imported state matches configuration and no unexpected changes occur.

3. Final Answer:

   Run terraform import for each security group, then run terraform plan to verify state matches configuration -> Option A

4. Quick Check:

   Import each resource, then verify with plan [OK]

Hint: Import individually and verify with plan to avoid surprises [OK]

Common Mistakes:

• Skipping plan after import
• Trying to create duplicates with apply
• Manually editing state file causing errors