Import block syntax (Terraform 1.5+) - Mini Project: Build & Apply

Importing Existing AWS S3 Bucket Using Terraform 1.5+ Import Block Syntax

📖 Scenario: You have an existing AWS S3 bucket created outside Terraform. You want to manage it using Terraform without recreating it.

🎯 Goal: Use Terraform 1.5+ import block syntax to import the existing AWS S3 bucket into Terraform state and configure it.

📋 What You'll Learn

Create a Terraform resource block for the AWS S3 bucket

Add an import block inside the resource to specify the bucket to import

Use the correct syntax for the import block introduced in Terraform 1.5+

Configure the bucket with versioning enabled

💡 Why This Matters

🌍 Real World

Managing existing cloud resources with Terraform allows teams to have infrastructure as code without recreating resources, reducing downtime and errors.

💼 Career

Cloud engineers and DevOps professionals often need to import existing resources into Terraform to maintain and automate infrastructure management.

1

Create AWS S3 bucket resource block

Create a Terraform resource block named aws_s3_bucket with the resource name my_bucket. Set the bucket attribute to my-existing-bucket.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  # Your code here
}

Hint

Use resource "aws_s3_bucket" "my_bucket" {} and set bucket = "my-existing-bucket".

2

Add import block to specify existing bucket

Inside the aws_s3_bucket.my_bucket resource block, add an import block. Set the id attribute to my-existing-bucket to specify the bucket to import.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-existing-bucket"
  # Add import block here
}

Hint

The import block syntax is new in Terraform 1.5+. Use import { id = "my-existing-bucket" } inside the resource.

3

Enable versioning on the bucket

Inside the aws_s3_bucket.my_bucket resource block, add a versioning block. Set enabled to true to enable versioning.

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-existing-bucket"

  import {
    id = "my-existing-bucket"
  }

  # Add versioning block here
}

Hint

Use versioning { enabled = true } inside the resource block to enable versioning.

4

Add provider configuration for AWS

Add a provider block for aws with the region set to us-east-1.

Terraform

provider "aws" {
  # Your code here
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-existing-bucket"

  import {
    id = "my-existing-bucket"
  }

  versioning {
    enabled = true
  }
}

Hint

Use provider "aws" { region = "us-east-1" } at the top of your Terraform file.

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