Bulk import strategies in Terraform - Commands & Configuration

Introduction

Sometimes you have existing cloud resources that Terraform did not create. Bulk import strategies help you bring those resources under Terraform management quickly and safely.

When you have many existing cloud resources created manually or by other tools and want to manage them with Terraform.

When migrating infrastructure to Terraform without downtime or resource recreation.

When you want to track and update existing resources using Terraform state.

When onboarding a new team to manage infrastructure with Terraform but resources already exist.

When you want to avoid deleting and recreating resources by importing them instead.

Config File - main.tf

main.tf

terraform {
  required_version = ">= 1.3.0"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.0"
    }
  }
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_s3_bucket" "example" {
  bucket = "example-bulk-import-bucket"
}

This Terraform configuration defines the AWS provider and a sample S3 bucket resource. The bucket name matches an existing bucket you want to import. This file is the base for importing existing resources into Terraform state.

Commands

Initialize Terraform in the current directory to download providers and set up the backend.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding hashicorp/aws versions matching ">= 4.0"...

- Installing hashicorp/aws v4.50.0...

- Installed hashicorp/aws v4.50.0 (signed by HashiCorp)



Terraform has been successfully initialized!



You may now begin working with Terraform. Try running "terraform plan" to see

any changes that are required for your infrastructure. All Terraform commands

should now work.

Import the existing S3 bucket named 'example-bulk-import-bucket' into Terraform state under the resource 'aws_s3_bucket.example'.

Terminal

terraform import aws_s3_bucket.example example-bulk-import-bucket

Expected Output

aws_s3_bucket.example: Importing from ID "example-bulk-import-bucket"...

aws_s3_bucket.example: Import prepared!

  Prepared aws_s3_bucket for import

aws_s3_bucket.example: Refreshing state... [id=example-bulk-import-bucket]



Import successful!



The resources that were imported are now in your Terraform state and will

be managed by Terraform.

Check the Terraform plan to verify that the imported resource matches the configuration and no changes are needed.

Terminal

terraform plan

Expected Output

Refreshing Terraform state in-memory prior to plan...



No changes. Infrastructure is up-to-date.



This means that Terraform did not detect any differences between your

configuration and real physical resources that exist. Your infrastructure

matches the configuration.

List all resources currently tracked in the Terraform state to confirm the import.

Terminal

terraform state list

Expected Output

aws_s3_bucket.example

Key Concept

If you remember nothing else from this pattern, remember: Terraform import links existing resources to your configuration so you can manage them without recreating.

Common Mistakes

Trying to import a resource without defining it in the Terraform configuration file.

Terraform import requires the resource block to exist in the configuration to map the imported resource correctly.

First define the resource in your .tf file with the correct type and name, then run terraform import.

Importing resources one by one manually for a large number of resources.

This is time-consuming and error-prone for many resources.

Use scripting or automation to run terraform import commands in bulk, or use tools that generate import scripts.

Not running terraform plan after import to verify state matches configuration.

You might miss configuration drift or mismatches causing unintended changes on apply.

Always run terraform plan after import to confirm no unexpected changes.

Summary

Define the existing resource in Terraform configuration before importing.

Use terraform import to link existing resources to Terraform state.

Run terraform plan to verify the imported resource matches the configuration.

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