A backend determines where Terraform stores state and, for supported backends, how it coordinates operations such as locking. Backend configuration belongs to initialization rather than to a managed resource’s desired attributes. Changing a bucket resource does not automatically move Terraform’s state into that bucket.
Plan a migration with a verified backup, permissions and a clear source and destination. Backend configuration cannot use the ordinary input variables and locals evaluated for resources. Credentials deserve a separate secure path because saved backend settings and plan files can retain them. These questions assess migration choices without contacting a remote state service.
A backend migration needs review of state storage, permissions and recovery.