Import block syntax (Terraform 1.5+) - Commands & Configuration

Introduction

Sometimes you have existing resources created outside Terraform and want to manage them with Terraform. The import block syntax in Terraform 1.5+ lets you declare these imports inside your configuration, so Terraform knows about them before you apply changes.

When you have a cloud resource created manually and want Terraform to manage it without recreating it.

When you want to keep your Terraform state in sync with resources created by other teams or tools.

When migrating existing infrastructure to Terraform management gradually.

When you want to automate importing resources as part of your Terraform workflow.

When you want to avoid running separate import commands manually.

Config File - main.tf

main.tf

terraform {
  required_version = ">= 1.5"
}

resource "aws_s3_bucket" "example" {
  bucket = "my-example-bucket"
  acl    = "private"
}

import {
  to = aws_s3_bucket.example
  id = "my-example-bucket"
}

This Terraform file defines an AWS S3 bucket resource named example. The import block tells Terraform to link the existing S3 bucket named my-example-bucket to this resource in the state. This way, Terraform knows it manages this bucket without creating a new one.

The terraform block ensures the Terraform version is 1.5 or higher, which supports the import block syntax.

Commands

This command initializes the Terraform working directory, downloads necessary providers, and prepares Terraform to run.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/aws...

- Installing hashicorp/aws v4.0.0...

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



Terraform has been successfully initialized!



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

This command shows what Terraform will do. Since the import block links an existing resource, Terraform will not try to create or destroy it.

Terminal

terraform plan

Expected Output

No changes. Infrastructure is up-to-date.



This means that Terraform did not detect any changes to apply.

This command applies the configuration. Because the resource is imported, Terraform will manage it without creating or deleting it.

Terminal

terraform apply -auto-approve

Expected Output

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



Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

→

-auto-approve - Automatically approves the apply without asking for confirmation

Key Concept

If you remember nothing else, remember: the import block in Terraform 1.5+ lets you declare existing resources inside your config so Terraform manages them without manual import commands.

Common Mistakes

Not specifying the correct resource address in the import block's 'to' field.

Terraform won't link the existing resource correctly, causing errors or attempts to recreate the resource.

Use the exact resource name and type as declared in your Terraform configuration for the 'to' field.

Using Terraform version below 1.5 which does not support import blocks.

Terraform will fail to parse the import block and show syntax errors.

Ensure Terraform version is 1.5 or higher by setting 'required_version' in the terraform block and upgrading Terraform.

Not running 'terraform init' before 'terraform plan' or 'apply'.

Terraform won't have the necessary providers and setup, causing errors.

Always run 'terraform init' first to prepare the working directory.

Summary

Write an import block in your Terraform config to link existing resources to Terraform state.

Run 'terraform init' to prepare your environment before planning or applying.

Use 'terraform plan' to verify no unexpected changes will happen.

Apply with 'terraform apply' to start managing the imported resource.

Practice

1. What is the main purpose of the import block in Terraform 1.5+?

easy

A. To create new resources automatically

B. To delete resources from the cloud provider

C. To let Terraform track existing resources without recreating them

D. To backup Terraform state files

Solution

1. Step 1: Understand the import block purpose

   The import block is designed to connect Terraform state with existing cloud resources.

2. Step 2: Differentiate from other actions

   It does not create or delete resources but tracks them to avoid recreation.

3. Final Answer:

   To let Terraform track existing resources without recreating them -> Option C

4. Quick Check:

   Import block = track existing resources [OK]

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

Common Mistakes:

• Thinking import creates new resources
• Confusing import with resource deletion
• Assuming import backs up state files

2. Which of the following is the correct syntax for an import block in Terraform 1.5+?

easy

A. import {
target = aws_instance.example
value = "i-1234567890abcdef0"
}

B. import {
to = aws_instance.example
id = "i-1234567890abcdef0"
}

C. import {
resource = aws_instance.example
key = "i-1234567890abcdef0"
}

D. import {
name = aws_instance.example
identifier = "i-1234567890abcdef0"
}

Solution

1. Step 1: Recall import block keys

   The import block uses to for the Terraform resource and id for the cloud resource ID.

2. Step 2: Match syntax with options

   Only import { to = aws_instance.example id = "i-1234567890abcdef0" } uses to and id correctly.

3. Final Answer:

   import { to = aws_instance.example id = "i-1234567890abcdef0" } -> Option B

4. Quick Check:

   Import keys = to and id [OK]

Hint: Remember keys: to = resource, id = cloud ID [OK]

Common Mistakes:

• Using wrong keys like resource or target
• Confusing id with identifier
• Missing quotes around the id value

3. Given this import block:

import {
  to = aws_s3_bucket.mybucket
  id = "my-existing-bucket"
}

What will Terraform do after applying this import block?

medium

A. Track the existing S3 bucket 'my-existing-bucket' without creating it

B. Create a new S3 bucket named 'my-existing-bucket'

C. Delete the S3 bucket 'my-existing-bucket'

D. Throw a syntax error due to missing resource configuration

Solution

1. Step 1: Understand import block effect

   The import block links Terraform state to an existing resource by its ID without creating or deleting it.

2. Step 2: Confirm behavior after import

   Terraform will track the existing bucket named 'my-existing-bucket' safely.

3. Final Answer:

   Track the existing S3 bucket 'my-existing-bucket' without creating it -> Option A

4. Quick Check:

   Import block = track existing resource [OK]

Hint: Import links state to existing resource, no creation [OK]

Common Mistakes:

• Assuming import creates new resources
• Thinking import deletes resources
• Confusing import with resource configuration

4. You wrote this import block:

import {
  to = aws_instance.web
  id = i-0abcd1234efgh5678
}

Terraform gives an error when applying. What is the likely cause?

medium

A. Terraform 1.5+ does not support import blocks

B. The to value should be the cloud resource ID

C. The import block must be inside a resource block

D. The id value is missing quotes

Solution

1. Step 1: Check syntax for id value

   The id value must be a string, so it requires quotes around it.

2. Step 2: Identify error cause

   Missing quotes around i-0abcd1234efgh5678 causes a syntax error.

3. Final Answer:

   The id value is missing quotes -> Option D

4. Quick Check:

   id value must be quoted string [OK]

Hint: Always quote id values in import blocks [OK]

Common Mistakes:

• Not quoting string IDs
• Confusing to and id values
• Placing import block inside resource block

5. You want to import an existing Azure resource group with ID "/subscriptions/123/resourceGroups/mygroup" into Terraform resource azurerm_resource_group.main. Which import block is correct and follows best practices?

hard

A. import {
to = azurerm_resource_group.main
id = "/subscriptions/123/resourceGroups/mygroup"
}

resource "azurerm_resource_group" "main" {
name = "mygroup"
location = "eastus"
}

B. import {
to = azurerm_resource_group.main
id = "mygroup"
}

resource "azurerm_resource_group" "main" {
name = "mygroup"
location = "eastus"
}

C. import {
to = azurerm_resource_group.main
id = "/subscriptions/123/resourceGroups/mygroup"
}

resource "azurerm_resource_group" "main" {
location = "eastus"
}

D. import {
to = azurerm_resource_group.main
id = "mygroup"
}

resource "azurerm_resource_group" "main" {
location = "eastus"
}

Solution

1. Step 1: Use full resource ID in import block

   The id must be the full Azure resource ID string to correctly identify the resource.

2. Step 2: Provide matching resource configuration

   After import, the resource block must include all required attributes like name and location to manage the resource safely.

3. Final Answer:

   Import block with full ID and resource block with name and location -> Option A

4. Quick Check:

   Full ID + matching config = correct import [OK]

Hint: Use full resource ID and matching config after import [OK]

Common Mistakes:

• Using partial ID instead of full resource ID
• Omitting required resource attributes after import
• Assuming import block replaces resource configuration