How to fix Terraform 'resource already exists' errors without deleting anything

When Terraform throws an AlreadyExists or creation conflict error, the root cause is typically a mismatch between the provider's known objects and Terraform's state, not a broken infrastructure. Terraform operates on two sources of truth: the desired configuration and the state file that tracks which remote objects it manages. If a resource exists remotely but lacks an entry in the state, Terraform plans a create, which the provider then rejects. The recommended fix involves four steps: confirming the remote resource exists, understanding why Terraform lacks ownership, importing the resource to link it to the correct state address, and running a revised plan to verify reconciliation. Blindly deleting resources or running imports without investigation can duplicate ownership disputes or cause further drift.