Question

A team manages several S3 buckets using a single resource block. They currently use `count` with a list of bucket names in a variable. When they remove a name from the middle of the list and run `terraform plan`, Terraform proposes destroying and recreating multiple buckets that were not intended to change. Which change to the configuration best prevents this behavior while still iterating over the collection?

Accepted Answer

Refactor the resource to use `for_each` over a map or set of bucket names so each instance is keyed by a stable string rather than a numeric index.

Answer

Add a `depends_on` block referencing the S3 bucket resource so Terraform preserves ordering during the apply.

Answer

Add a `lifecycle` block with `create_before_destroy = true` to avoid the recreation of the remaining buckets.

Answer

Sort the list variable alphabetically so the indexes remain consistent between plans.