Import limitations and considerations in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the Terraform import command do?

It brings existing infrastructure resources into Terraform's management by adding them to the state file without changing the actual resource.

intermediate

Why can't Terraform import multiple resources at once?

Terraform import works on one resource at a time because each resource requires a unique address and ID to be mapped correctly in the state file.

beginner

What must you do after importing a resource to Terraform?

You must write the matching Terraform configuration code for the imported resource to avoid discrepancies between the state and configuration.

intermediate

Can Terraform import resources that are not supported by the provider?

No, Terraform can only import resources that the provider supports and has import functionality for.

advanced

What is a common consideration when importing resources with dependencies?

You should import resources in the correct order (dependencies first) to maintain relationships and avoid errors in the state.

What does Terraform import update?

A The Terraform state file

B The cloud provider's resource configuration

C The Terraform configuration files

D The Terraform backend settings

Terraform import updates the state file to include the existing resource but does not change configuration files or the actual resource.

Which of the following is a limitation of Terraform import?

A It requires manual configuration code after import

B It automatically generates configuration code

C It can import multiple resources simultaneously

D It changes the resource in the cloud provider

Terraform import does not generate configuration code; you must write it manually to match the imported resource.

If a resource has dependencies, what should you do when importing?

A Ignore dependencies during import

B Import the resource without dependencies first

C Import the dependent resources first

D Import all resources at once

Import resources without dependencies first (i.e., the dependencies) to ensure the state reflects correct relationships and avoids errors.

Can Terraform import a resource that the provider does not support?

A Only if manually configured

B No, only supported resources can be imported

C Yes, always

D Yes, but only with plugins

Terraform import only works for resources supported by the provider with import functionality.

What happens if Terraform configuration does not match the imported resource?

A Terraform will automatically fix the configuration

B Terraform deletes the resource

C Terraform ignores the mismatch

D Terraform will show a difference and may try to change the resource

Terraform detects differences and may attempt to update the resource to match the configuration.

Explain the key limitations and considerations when using Terraform import.

Think about what import changes and what you must do after.

Describe the steps you should take after importing a resource into Terraform.

Consider how to keep Terraform state and config consistent.

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