Bulk import strategies in Terraform - Step-by-Step Execution

Process Flow - Bulk import strategies

Identify resources to import

↓

Prepare import commands list

↓

Run terraform import for each resource

↓

Verify imported state

↓

Write resource blocks in config

↓

Run terraform plan to confirm sync

↓

Done

This flow shows how to import many resources into Terraform state step-by-step, from identifying resources to confirming they are managed.

Execution Sample

Terraform

terraform import aws_instance.example i-1234567890abcdef0
terraform import aws_s3_bucket.example my-bucket-name

These commands import an AWS EC2 instance and an S3 bucket into Terraform state.

Process Table

Step	Action	Resource	Command	Result
1	Identify resources	EC2 instance	-	Found instance i-1234567890abcdef0
2	Identify resources	S3 bucket	-	Found bucket my-bucket-name
3	Prepare import commands	EC2 instance	terraform import aws_instance.example i-1234567890abcdef0	Ready to import
4	Prepare import commands	S3 bucket	terraform import aws_s3_bucket.example my-bucket-name	Ready to import
5	Run import	EC2 instance	terraform import aws_instance.example i-1234567890abcdef0	Imported successfully
6	Run import	S3 bucket	terraform import aws_s3_bucket.example my-bucket-name	Imported successfully
7	Verify state	All	terraform state list	Resources listed in state
8	Write config	All	Write resource blocks in .tf files	Config matches imported resources
9	Run plan	All	terraform plan	No changes, state and config in sync
10	Done	-	-	Bulk import complete

💡 All resources imported and Terraform state matches configuration

Status Tracker

Variable	Start	After Step 5	After Step 7	After Step 9	Final
terraform state	empty	contains EC2 and S3	verified resources listed	matches config	stable and synced
configuration files	empty	empty	empty	resource blocks added	complete

Key Moments - 3 Insights

Why do we need to write resource blocks in config after importing?

Because terraform import only adds resources to state, but config files must define resources for Terraform to manage them. See execution_table step 8.

What happens if the resource ID is wrong during import?

The import command will fail and not add the resource to state. You must use the correct ID as shown in steps 3 and 4.

Why run terraform plan after import and writing config?

To confirm that the imported state matches the config and no unexpected changes will occur. See step 9.

Visual Quiz - 3 Questions

Look at the execution table, what is the result of running 'terraform import' for the EC2 instance at step 5?

A Import failed

B Imported successfully

C Resource not found

D No changes detected

💡 Hint

Check the 'Result' column at step 5 in the execution_table.

At which step do we verify that the Terraform state lists all imported resources?

A Step 3

B Step 9

C Step 7

D Step 2

💡 Hint

Look for the step with action 'Verify state' in the execution_table.

If you skip writing resource blocks in config, what will happen when you run 'terraform plan'?

A Terraform will try to delete imported resources

B Terraform will error due to missing config

C Terraform will show no changes

D Terraform will import resources again

💡 Hint

Refer to key_moments about why config is needed after import and step 9 in execution_table.

Concept Snapshot

Bulk import in Terraform:
1. Identify existing resources.
2. Prepare and run 'terraform import' commands.
3. Write matching resource blocks in config files.
4. Run 'terraform plan' to confirm state and config sync.
Always import before writing config to avoid conflicts.

Full Transcript

Bulk import strategies in Terraform involve identifying existing cloud resources, preparing import commands for each, running these commands to add resources to Terraform state, then writing resource blocks in configuration files to manage them. After importing and writing config, running 'terraform plan' confirms that the state and config are synchronized with no unexpected changes. This process ensures Terraform can manage existing infrastructure safely and effectively.

Practice

1. What is the main purpose of using bulk import strategies in Terraform?

easy

A. To automatically generate Terraform code for new resources

B. To create new resources faster than usual

C. To delete multiple resources simultaneously

D. To efficiently bring many existing resources under Terraform management at once

Solution

1. Step 1: Understand Terraform import

   Terraform import lets you bring existing cloud resources into Terraform state so you can manage them.

2. Step 2: Recognize bulk import purpose

   Bulk import strategies help import many resources quickly instead of one by one.

3. Final Answer:

   To efficiently bring many existing resources under Terraform management at once -> Option D

4. Quick Check:

   Bulk import = manage many existing resources [OK]

Hint: Bulk import means importing many existing resources at once [OK]

Common Mistakes:

• Thinking bulk import creates new resources
• Confusing import with resource deletion
• Assuming import auto-generates Terraform code

2. Which Terraform command is used to import a resource into the state file?

easy

A. terraform import

B. terraform plan

C. terraform init

D. terraform apply

Solution

1. Step 1: Recall Terraform commands

   terraform apply creates or updates resources, terraform init initializes, terraform plan previews changes.

2. Step 2: Identify import command

   terraform import is the command that brings existing resources into Terraform state.

3. Final Answer:

   terraform import -> Option A

4. Quick Check:

   Import command = terraform import [OK]

Hint: Import existing resources with 'terraform import' command [OK]

Common Mistakes:

• Using terraform apply to import
• Confusing init with import
• Trying terraform plan to import

3. Given this script snippet to bulk import AWS EC2 instances:

for id in i-12345678 i-87654321; do terraform import aws_instance.example_$id $id; done

What will be the result after running this script?

medium

A. Terraform will create new instances instead of importing

B. Only the first instance will be imported, second will fail

C. Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321

D. The script will cause a syntax error and not run

Solution

1. Step 1: Analyze the for loop

   The loop iterates over two instance IDs: i-12345678 and i-87654321.

2. Step 2: Understand terraform import usage

   Each iteration runs terraform import with resource name aws_instance.example_$id and the ID as argument, importing both instances.

3. Final Answer:

   Both instances will be imported with resource names aws_instance.example_i-12345678 and aws_instance.example_i-87654321 -> Option C

4. Quick Check:

   Loop imports both instances correctly [OK]

Hint: Loop imports each resource with unique name using ID [OK]

Common Mistakes:

• Assuming only one import runs
• Thinking terraform creates new instances
• Believing script syntax is invalid

4. You wrote a bulk import script but get errors: "Error: Resource name must not contain '-'". What is the likely cause?

medium

A. Using resource names with dashes (-) which Terraform disallows

B. Missing terraform init before import

C. Incorrect AWS credentials causing import failure

D. Trying to import resources that do not exist

Solution

1. Step 1: Understand Terraform resource naming rules

   Terraform resource names must use underscores (_) not dashes (-).

2. Step 2: Identify cause of error

   The error says resource name must not contain '-', so using dashes in resource names causes this error.

3. Final Answer:

   Using resource names with dashes (-) which Terraform disallows -> Option A

4. Quick Check:

   Resource names cannot have '-' [OK]

Hint: Use underscores (_) in resource names, not dashes (-) [OK]

Common Mistakes:

• Ignoring naming rules and using dashes
• Assuming missing init causes this error
• Blaming credentials for naming errors

5. You want to bulk import 100 existing Azure VMs into Terraform. Which approach best follows Terraform bulk import best practices?

hard

A. Run terraform import once with all VM IDs separated by commas

B. Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files

C. Manually import each VM one by one using terraform import command

D. Create new Terraform resources and delete existing VMs to sync state

Solution

1. Step 1: Understand bulk import best practice

   Bulk import works best with automation scripts looping over resource IDs to import each resource.

2. Step 2: Match Terraform configuration

   Terraform requires matching resource blocks in config files for imported resources to manage them properly.

3. Step 3: Evaluate options

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files uses scripting and matching config, Run terraform import once with all VM IDs separated by commas is invalid syntax, Manually import each VM one by one using terraform import command is slow manual work, Create new Terraform resources and delete existing VMs to sync state deletes resources which is unsafe.

4. Final Answer:

   Write a script that loops over VM IDs, runs terraform import for each, and maintains matching Terraform config files -> Option B

5. Quick Check:

   Automate import with matching config files [OK]

Hint: Automate imports with scripts and matching config files [OK]

Common Mistakes:

• Trying to import multiple IDs in one command
• Manually importing many resources without automation
• Deleting resources instead of importing