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.