Import limitations and considerations in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import an existing AWS S3 bucket into Terraform state.

Terraform

terraform import aws_s3_bucket.example [1]

Drag options to blanks, or click blank then click option'

Abucket_name

Bbucket_id

Caws_s3_bucket.example

Dexample_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Terraform resource name instead of the actual bucket name.

Using a placeholder like 'bucket_id' instead of the real identifier.

You must specify the actual bucket name when importing, not the resource name or ID placeholder.

2fill in blank

medium

Complete the code to import an AWS EC2 instance with the correct ID format.

Terraform

terraform import aws_instance.web [1]

Drag options to blanks, or click blank then click option'

Ai-1234567890abcdef0

Binstance-1234

Cweb-instance

Daws_instance.web

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource name or tag instead of the instance ID.

Using an incorrect ID format.

The EC2 instance ID must be in the format starting with 'i-' followed by hexadecimal characters.

3fill in blank

hard

Fix the error in the import command by choosing the correct resource address format.

Terraform

terraform import [1] my-resource-id

Drag options to blanks, or click blank then click option'

Amy_bucket.aws_s3_bucket

Baws_s3_bucket/my_bucket

Caws_s3_bucket.my_bucket

Dmy_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using slashes instead of dots in resource addresses.

Reversing resource type and name order.

The correct resource address format is resource_type.resource_name with a dot separator.

4fill in blank

hard

Fill both blanks to correctly import a resource and specify its ID.

Terraform

terraform import [1] [2]

Drag options to blanks, or click blank then click option'

Aaws_db_instance.prod_db

Bdb-prod-01

Cprod_db_instance

Daws_db_instance/db-prod-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using slashes in resource address.

Using resource name instead of resource ID.

The first blank is the Terraform resource address, and the second blank is the actual resource ID in AWS.

5fill in blank

hard

Fill the blanks to import an AWS IAM user with the correct resource address and user name.

Terraform

terraform import [1] [2]

Drag options to blanks, or click blank then click option'

Aaws_iam_user.admin

Badmin-user

Caws_iam_user/admin-user

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using slashes in resource address.

Using incorrect user name format.

The resource address uses dot notation (blank 1), the user name is the actual AWS IAM user name (blank 2).

Practice

1. What is the main purpose of the terraform import command?

easy

A. To delete resources from the cloud provider

B. To create new resources from scratch

C. To bring existing resources under Terraform management without recreating them

D. To update Terraform itself to the latest version

Solution

1. Step 1: Understand the role of terraform import

   The terraform import command is used to take resources that already exist outside Terraform and bring them into Terraform's control without deleting or recreating them.

2. Step 2: Differentiate from other commands

   Creating new resources is done with terraform apply, deleting is done with terraform destroy, and updating Terraform is unrelated to resource import.

3. Final Answer:

   To bring existing resources under Terraform management without recreating them -> Option C

4. Quick Check:

   terraform import = bring existing resources under control [OK]

Hint: Import means adopt existing resources, not create new ones [OK]

Common Mistakes:

• Thinking import creates new resources
• Confusing import with resource deletion
• Assuming import updates Terraform version

2. Which of the following is required before running terraform import for a resource?

easy

A. The resource must be deleted first

B. The resource must be created by Terraform previously

C. Terraform must be initialized with terraform init after import

D. The resource configuration must exist in the Terraform files

Solution

1. Step 1: Check Terraform import requirements

   Before importing, Terraform needs a matching resource block in the configuration files to map the imported resource to.

2. Step 2: Understand other options

   The resource should not be deleted before import; terraform init is run before import, not after; and the resource does not need to be created by Terraform previously.

3. Final Answer:

   The resource configuration must exist in the Terraform files -> Option D

4. Quick Check:

   Config must exist before import [OK]

Hint: Write resource config first, then import [OK]

Common Mistakes:

• Trying to import without resource config
• Deleting resource before import
• Running terraform init after import

3. Given this Terraform resource configuration:

resource "aws_s3_bucket" "mybucket" {
  bucket = "my-existing-bucket"
}

What happens if you run terraform import aws_s3_bucket.mybucket my-existing-bucket?

medium

A. Terraform imports the existing S3 bucket and manages it without changes

B. Terraform deletes the existing bucket and creates a new one

C. Terraform throws an error because the bucket name is missing

D. Terraform creates a duplicate bucket with a different name

Solution

1. Step 1: Match resource config and import command

   The resource block matches the bucket name used in the import command, so Terraform will link the existing bucket to this resource.

2. Step 2: Understand import behavior

   Import does not delete or recreate resources; it only brings them under Terraform management.

3. Final Answer:

   Terraform imports the existing S3 bucket and manages it without changes -> Option A

4. Quick Check:

   Import links existing resource without changes [OK]

Hint: Import links existing resource, no deletion [OK]

Common Mistakes:

• Assuming import deletes or recreates resource
• Confusing import with apply
• Using wrong resource ID format

4. You run terraform import aws_instance.web i-1234567890abcdef0 but get an error saying the resource ID format is invalid. What is the most likely cause?

medium

A. Terraform was not initialized with terraform init

B. The resource ID does not match the expected format for the AWS provider

C. The resource configuration block is missing in Terraform files

D. The AWS instance does not exist in the cloud

Solution

1. Step 1: Check resource ID format

   Terraform import requires the resource ID to match the provider's expected format exactly. An invalid format causes errors.

2. Step 2: Differentiate from other causes

   Missing config causes different errors; uninitialized Terraform causes different errors; non-existent resource causes not found errors, not format errors.

3. Final Answer:

   The resource ID does not match the expected format for the AWS provider -> Option B

4. Quick Check:

   Invalid ID format causes import error [OK]

Hint: Check provider docs for correct ID format before import [OK]

Common Mistakes:

• Ignoring ID format requirements
• Assuming missing config causes format error
• Skipping terraform init before import

5. You want to import multiple existing resources of the same type but with different IDs into Terraform. Which approach best handles this scenario?

hard

A. Write separate resource blocks with unique names and import each resource individually

B. Write one resource block and import all IDs at once using a comma-separated list

C. Use a single resource block with a list of IDs and import once

D. Import resources without any configuration blocks and Terraform will auto-discover them

Solution

1. Step 1: Understand Terraform resource uniqueness

   Each resource block must have a unique name to represent a single resource instance in Terraform.

2. Step 2: Import multiple resources properly

   To import multiple resources, create multiple resource blocks with unique names and import each resource ID separately.

3. Step 3: Eliminate incorrect options

   Terraform does not support importing multiple IDs at once in one resource block or auto-discovery without config.

4. Final Answer:

   Write separate resource blocks with unique names and import each resource individually -> Option A

5. Quick Check:

   One resource block per resource, import individually [OK]

Hint: One resource block per resource, import separately [OK]

Common Mistakes:

• Trying to import multiple IDs in one resource block
• Assuming Terraform auto-discovers resources
• Using comma-separated IDs in import command