Question

A DevOps engineer must bring a manually-created AWS S3 bucket under Terraform management using the legacy `terraform import` command (not import blocks). The engineer runs `terraform import aws_s3_bucket.logs my-existing-bucket` in a directory that currently has no resource block for that bucket. What happens, and what must be done first?

Accepted Answer

The import fails or leaves an orphaned state entry because no matching resource block exists; the engineer must first write an `aws_s3_bucket.logs` resource block in configuration, then run import.

Answer

The import succeeds and Terraform automatically generates the full resource configuration in the .tf files, so no manual work is needed.

Answer

The import fails and Terraform prompts interactively to create the resource block for you before continuing.

Answer

The import succeeds and Terraform manages the bucket entirely from state, so a resource block is never required.