Error map
Backend configuration changed (migrate or reconfigure) Terraform: Error: Backend configuration changed — A change in the backend configuration has been detected, which may require migrating existing state
Terraform · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked
Another Terraform run holds the state lock, or a previous run crashed and left the lock behind.
Terraform: # aws_instance.web is tainted, so must be replaced — -/+ destroy and then create replacement
A previous apply failed during creation, so Terraform marked the resource tainted and will recreate it.
Terraform: Error: Failed to get existing workspaces: S3 bucket "my-tf-state" does not exist / NoSuchBucket: The specified bucket does not exist
The S3 bucket configured as the state backend doesn't exist (or is in another region/account).
Terraform: Error: Backend initialization required, please run "terraform init" — Reason: Initial configuration of the requested backend "s3"
Terraform needs `terraform init` to set up the backend (new directory, changed backend config, missing `.terraform`).
Terraform: Error: Error acquiring the state lock: ResourceNotFoundException: Requested resource not found / failed to retrieve lock info
The S3 backend's `dynamodb_table` doesn't exist, so locking fails.
Terraform: Error: state snapshot was created by Terraform v1.9.0, which is newer than current v1.6.6; upgrade to Terraform v1.9.0 or greater to work with this state
The remote/local state was last written by a newer Terraform CLI than the one you're running.
Terraform: Error: Failed to load state: AccessDenied: Access Denied / Error refreshing state: AccessDenied status code: 403
Terraform can't read/write the S3 bucket (or DynamoDB table) that stores state — IAM permissions or wrong credentials/role.
Terraform: Error: Cannot import non-existent remote object — While attempting to import an existing object to "aws_s3_bucket.logs", the provider detected that no object exists with the given id
`terraform import` (or an import block) used an ID that the provider can't find.
Terraform: Error: Kubernetes cluster unreachable: Get "http://localhost/version": dial tcp 127.0.0.1:80: connect: connection refused
The Kubernetes/Helm provider can't connect to the cluster (no config, cluster not ready at plan time, expired credentials).
Terraform: Error: Failed to select workspace: workspace "staging" doesn't exist / Currently selected workspace "x" does not exist
The workspace you selected (or that `.terraform/environment` points to) isn't present in the backend.
Terraform: Error: Provider configuration not present — its original provider configuration is required, but it has been removed
A resource in state needs a provider configuration (alias) that no longer exists in the code.
Terraform: Error: Invalid target address — No matching objects found. To view the available instances, use "terraform state list"
A state/target command referenced an address that doesn't exist in state.
Two steps away (29)
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
Error: Too many re-renders. React limits the number of renders to prevent an infinite loop.
A state update runs during render, which triggers another render, which updates state again — forever.
Terraform: Error: creating S3 Bucket (my-bucket): BucketAlreadyOwnedByYou / EntityAlreadyExists: Role with name x already exists
The resource exists outside Terraform's state (created manually or by another stack), so create fails.
Terraform: Error: waiting for RDS DB Instance create: timeout while waiting for state to become 'available' (last state: 'creating', timeout: 40m0s)
The resource didn't reach the target state before the provider's timeout.
Terraform: Error: Provider produced inconsistent result after apply — When applying changes to aws_x.y, provider produced an unexpected new value: Root resource was present, but now absent
After creating/updating a resource, the provider returned values that don't match what Terraform planned — usually a provider bug…
Terraform: Error: No valid credential sources found — failed to refresh cached credentials, no EC2 IMDS role found / Error: configuring Terraform AWS Provider: no valid credential sources
The AWS provider found no credentials (env vars, shared config, SSO, role, instance profile).
Terraform: Error: creating EC2 Instance: UnauthorizedOperation: You are not authorized to perform this operation. User: arn:aws:iam::123:user/ci is not authorized to perform: ec2:RunInstances
The IAM identity used by Terraform lacks a permission needed for that resource.
Terraform: Error: Invalid AWS Region: us-east-3 / Error: configuring Terraform AWS Provider: validating provider credentials: operation error STS: GetCallerIdentity
The `region` is invalid/unavailable, or the provider can't reach AWS endpoints to validate credentials.
Terraform: Error: Failed to query available provider packages — Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints
`terraform init` can't find a provider version matching your constraints (or can't reach the registry).
Terraform: Error: Failed to install provider — Error while installing hashicorp/aws v5.40.0: could not query provider registry / Get "https://releases.hashicorp.com/...": dial tcp: i/o timeout
Terraform found the provider version but couldn't download/verify the package.
Terraform: Error: Module not installed — This module is not yet installed. Run "terraform init" to install all modules required by this configuration
A module block references a module that hasn't been downloaded to `.terraform/modules`.
Error response from daemon: client version 1.45 is too new. Maximum supported API version is 1.41
Your Docker CLI (or SDK) speaks a newer API version than the Docker daemon it’s talking to.
Terraform: Error: Unsupported Terraform Core version — This configuration does not support Terraform version 1.5.7
The installed Terraform CLI doesn't satisfy `required_version` in the configuration (or a module).
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
Terraform: Error: Output refers to sensitive values — a root module output containing sensitive data must be explicitly marked as sensitive
An output (or module output) exposes a value derived from a sensitive variable/attribute without `sensitive = true`.
Terraform: Error: deleting S3 Bucket (my-bucket): BucketNotEmpty: The bucket you tried to delete is not empty
Terraform can't delete an S3 bucket that still holds objects (or versions).
Terraform: Error: reading EC2 Instance (i-0abc): couldn't find resource / 404 ResourceNotFound during refresh
A resource tracked in state no longer exists in the cloud (deleted manually) or can't be read with current credentials.
Terraform: Error: Moved object still exists — This statement declares a move from aws_x.old, but that resource instance is still declared at main.tf
A `moved` block points at an address that is still present in the configuration.
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
helm install was run with a release name that already exists in the namespace (even a failed one).
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
A previous Helm operation on this release was interrupted and left it in a pending-install/pending-upgrade state, so Helm refuses…
rendered manifests contain a resource that already exists. Unable to continue with install: ... invalid ownership metadata
Helm wants to create an object that already exists but isn’t labelled as belonging to this release.
Terraform: Error: building AzureRM Client: obtaining subscription ID / Please run 'az login' to setup account
The AzureRM provider can't find Azure credentials or a subscription.
Terraform: Error: Inconsistent dependency lock file — provider x: required by this configuration but no version is selected
The .terraform.lock.hcl file doesn’t match the providers/versions your configuration now requires, or init wasn’t run.
Terraform: Error: Reference to undeclared resource / Reference to undeclared input variable
The configuration refers to a resource, data source, variable or module output that isn’t declared in this module.
Terraform: Error: Instance cannot be destroyed — Resource aws_db_instance.prod has lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed
The plan would destroy a resource protected with `lifecycle { prevent_destroy = true }`.
docker: invalid reference format (repository name must be lowercase)
Docker couldn’t parse the image name — uppercase letters, spaces, an empty variable, or a misplaced option.
Error response from daemon: No such container
The container name or ID you used doesn’t exist on this Docker host — it was removed, has another name, or you’re talking to a di…
Error response from daemon: Container X is not running
You tried to exec into or interact with a container that has stopped.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError