Platform & DevOps·Infrastructure described in a file
you changed one field the API cannot update in place, and the plan quietly says destroy then create.
Resource replacement
Also calledforce new, destroy and recreate, immutable update
The tool deciding a change can only be made by deleting and recreating a resource, because the underlying API has no in-place update for that attribute. On a stateless resource it is invisible; on a database, a volume or anything holding an address it is an outage or a data loss. The line to look for in a plan is the one saying the change forces replacement, and it is why plans should be read from the bottom of the risk order upwards.