Writing configuration for imported resources in Terraform - Step-by-Step Execution

Process Flow - Writing configuration for imported resources

Identify existing resource

↓

Import resource using CLI

↓

Write matching Terraform config

↓

Run terraform plan

↓

Verify no changes needed

↓

Manage resource with Terraform

This flow shows how to bring an existing resource under Terraform management by importing it, writing matching config, and verifying no changes.

Execution Sample

Terraform

terraform import aws_s3_bucket.mybucket my-existing-bucket

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

Import an existing S3 bucket and write Terraform config to match it.

Process Table

Step	Action	CLI/Config	Terraform State	Result
1	Identify existing resource	N/A	No resource in state	Ready to import
2	Import resource	terraform import aws_s3_bucket.mybucket my-existing-bucket	State updated with resource	Resource tracked by Terraform
3	Write config	resource "aws_s3_bucket" "mybucket" { bucket = "my-existing-bucket" acl = "private" }	Config matches resource	Terraform knows resource details
4	Run terraform plan	terraform plan	State and config compared	No changes detected
5	Manage resource	terraform apply	State updated if needed	Resource managed by Terraform
6	Exit	N/A	State and config synced	Process complete

💡 No changes detected after plan, resource is fully managed

Status Tracker

Variable	Start	After Import	After Config Write	After Plan	Final
terraform_state	empty	contains aws_s3_bucket.mybucket	unchanged	unchanged	unchanged
configuration	empty	empty	contains aws_s3_bucket.mybucket config	unchanged	unchanged

Key Moments - 3 Insights

Why do I need to write the Terraform config after importing a resource?

Importing only adds the resource to Terraform state; without matching config, Terraform will try to delete or recreate it. See execution_table step 3 and 4.

What happens if the config does not match the imported resource?

Terraform plan will show changes to apply, possibly deleting or modifying the resource unexpectedly. See execution_table step 4.

Can I import multiple resources at once?

You must import each resource individually with its own import command and write matching config for each. See execution_table steps 2 and 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Terraform state after step 2?

A Contains the imported resource

B Empty, no resources tracked

C Matches the written config

D Shows planned changes

💡 Hint

Check the 'Terraform State' column in row for step 2

At which step does Terraform detect no changes needed?

A Step 2 - Import resource

B Step 3 - Write config

C Step 4 - Run terraform plan

D Step 5 - Manage resource

💡 Hint

Look at the 'Result' column for step 4 in execution_table

If the config does not match the imported resource, what will terraform plan show?

A No changes needed

B Planned changes to update or replace resource

C Errors and stops

D Resource removed from state

💡 Hint

Refer to key_moments about mismatched config and step 4 in execution_table

Concept Snapshot

Terraform import brings existing resources into state.
You must write matching config to avoid unwanted changes.
Run terraform plan to verify no changes.
Then manage resource normally with Terraform.

Full Transcript

To manage an existing cloud resource with Terraform, first identify the resource you want to import. Use the terraform import command to add it to Terraform's state file. This does not create configuration files, so you must write Terraform configuration that matches the imported resource's settings. After writing the config, run terraform plan to compare the state and config. If they match, no changes will be planned, meaning Terraform now fully manages the resource. This process prevents Terraform from trying to recreate or delete the resource. Always verify with terraform plan before applying changes.