Terraform import command - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to import an AWS S3 bucket named 'my-bucket' into Terraform state.

Terraform

terraform import [1] my-bucket

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

Aaws_lambda_function.func

Baws_instance.my_instance

Caws_vpc.main

Daws_s3_bucket.my-bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong resource type like aws_instance or aws_vpc.

Forgetting to specify the resource name after the resource type.

The correct resource type and name for importing an S3 bucket is aws_s3_bucket.my-bucket.

2fill in blank

medium

Complete the command to import an AWS EC2 instance with ID 'i-1234567890abcdef0' into Terraform state.

Terraform

terraform import [1] i-1234567890abcdef0

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

Aaws_instance.my_ec2

Baws_iam_role.role

Caws_security_group.sg

Daws_s3_bucket.my_bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong resource type like aws_s3_bucket or aws_security_group.

Using the instance ID as the resource name instead of the import ID.

The resource type for EC2 instances is aws_instance, so the correct import target is aws_instance.my_ec2.

3fill in blank

hard

Fix the error in the import command to correctly import an AWS VPC with ID 'vpc-0a1b2c3d4e5f6g7h8'.

Terraform

terraform import [1] vpc-0a1b2c3d4e5f6g7h8

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

Aaws_vpc.main

Baws_instance.main

Caws_subnet.main

Daws_route_table.main

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource types for instances or subnets instead of VPC.

Using incorrect resource names that do not exist in the configuration.

The correct resource type for a VPC is aws_vpc. Using aws_vpc.main matches the Terraform resource name.

4fill in blank

hard

Fill both blanks to import an AWS IAM role named 'my-role' with ARN 'arn:aws:iam::123456789012:role/my-role'.

Terraform

terraform import [1] [2]

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

Aaws_iam_role.my-role

Baws_iam_policy.my_policy

Carn:aws:iam::123456789012:role/my-role

Dmy-role

Attempts:

3 left

💡 Hint

Common Mistakes

Using the role name instead of the ARN for the import ID.

Using the wrong resource type like aws_iam_policy.

The import command requires the Terraform resource address aws_iam_role.my-role and the full ARN of the IAM role.

5fill in blank

hard

Fill both blanks to import an AWS RDS instance with identifier 'mydbinstance' into Terraform state.

Terraform

terraform import [1] [2]

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

Aaws_db_instance.mydb

Bmydbinstance

Caws_rds_instance.mydb

Daws_db_instance.mydbinstance

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect resource types like aws_rds_instance.

Using the wrong import ID or resource name.

The correct resource type is aws_db_instance.mydb and the import ID is the DB instance identifier mydbinstance.

Practice

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

easy

A. To connect existing cloud resources to Terraform management

B. To create new resources in the cloud

C. To delete resources managed by Terraform

D. To update Terraform version

Solution

1. Step 1: Understand the command's role

   The terraform import command is used to bring existing resources under Terraform's control without recreating them.

2. Step 2: Differentiate from other commands

   Unlike commands that create or delete resources, import only connects existing ones to Terraform state.

3. Final Answer:

   To connect existing cloud resources to Terraform management -> Option A

4. Quick Check:

   Import = Connect existing resources [OK]

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

Common Mistakes:

• Thinking import creates new resources
• Confusing import with terraform apply
• Assuming import deletes resources

2. Which of the following is the correct syntax to import an AWS S3 bucket named my-bucket into Terraform resource aws_s3_bucket.example?

easy

A. terraform import my-bucket aws_s3_bucket.example

B. terraform import aws_s3_bucket.example my-bucket

C. terraform import aws_s3_bucket.example aws_s3_bucket.my-bucket

D. terraform import example aws_s3_bucket.my-bucket

Solution

1. Step 1: Identify correct command order

   The syntax is terraform import <resource_address> <resource_id>. Here, resource address is aws_s3_bucket.example and ID is my-bucket.

2. Step 2: Match options to syntax

   terraform import aws_s3_bucket.example my-bucket matches the correct order: resource address first, then resource ID.

3. Final Answer:

   terraform import aws_s3_bucket.example my-bucket -> Option B

4. Quick Check:

   Import syntax = resource_address resource_id [OK]

Hint: Remember: import <resource_address> <resource_id> [OK]

Common Mistakes:

• Swapping resource address and ID
• Using resource type instead of address
• Adding extra prefixes to resource ID

3. Given this Terraform import command:
terraform import aws_instance.web i-1234567890abcdef0
What will Terraform do after running this command?

medium

A. Create a new AWS instance with ID i-1234567890abcdef0

B. Delete the AWS instance i-1234567890abcdef0

C. Add the existing AWS instance i-1234567890abcdef0 to Terraform state under aws_instance.web

D. Update the AWS instance i-1234567890abcdef0 with Terraform configuration

Solution

1. Step 1: Understand import effect on state

   The import command adds an existing resource to Terraform's state file without creating or deleting it.

2. Step 2: Clarify what happens to the resource

   The resource remains unchanged in the cloud; Terraform just tracks it as aws_instance.web.

3. Final Answer:

   Add the existing AWS instance i-1234567890abcdef0 to Terraform state under aws_instance.web -> Option C

4. Quick Check:

   Import adds resource to state, no creation or deletion [OK]

Hint: Import updates state, not cloud resources [OK]

Common Mistakes:

• Thinking import creates or deletes resources
• Assuming import applies configuration changes
• Confusing import with terraform apply

4. You ran terraform import aws_s3_bucket.example my-bucket but got an error: Resource aws_s3_bucket.example not found in configuration. What is the likely cause?

medium

A. The import command syntax is incorrect

B. The bucket my-bucket does not exist in AWS

C. Terraform version is outdated

D. The resource aws_s3_bucket.example is missing in Terraform files

Solution

1. Step 1: Analyze error message

   The error says the resource address is not found in configuration, meaning Terraform files lack aws_s3_bucket.example.

2. Step 2: Confirm resource presence

   Before import, Terraform must know the resource block to map the imported resource correctly.

3. Final Answer:

   The resource aws_s3_bucket.example is missing in Terraform files -> Option D

4. Quick Check:

   Resource must exist in config before import [OK]

Hint: Define resource in config before importing [OK]

Common Mistakes:

• Ignoring missing resource block
• Assuming import creates resource block
• Blaming AWS resource existence first

5. You imported an existing AWS security group with terraform import aws_security_group.sg sg-0a1b2c3d4e5f6g7h8. After import, your Terraform configuration does not match the actual security group rules. What should you do next?

hard

A. Manually update your Terraform configuration to match the imported resource

B. Run terraform apply immediately to fix the resource

C. Delete the imported resource from state and re-import

D. Nothing, Terraform will auto-sync configuration

Solution

1. Step 1: Understand import limitations

   Import adds the resource to state but does not update Terraform files to reflect actual settings.

2. Step 2: Align configuration with reality

   You must manually edit Terraform configuration to match the imported resource's current rules to avoid unwanted changes on apply.

3. Final Answer:

   Manually update your Terraform configuration to match the imported resource -> Option A

4. Quick Check:

   Update config after import to match resource [OK]

Hint: Edit config to match imported resource before apply [OK]

Common Mistakes:

• Expecting terraform apply to fix config automatically
• Deleting and re-importing unnecessarily
• Ignoring config mismatch risks