All Errors

The "No source for module" error occurs when Terraform cannot locate the module source you specified. This happens when the module path is missing, incorrect, or the modules have not been initialized. Resolving this requires verifying the source path and running terraform init.

The AddressSpaceOverlap error occurs when you attempt to create or peer Azure Virtual Networks (VNets) with overlapping CIDR address ranges. Azure requires all VNets and subnets to have non-overlapping IP address spaces.

This error occurs when for_each tries to iterate over resource attributes that are not known until apply time. Terraform requires all for_each keys to be known during the planning phase to predict resource creation.

This error occurs when Terraform attempts to create an AWS ECR repository that already exists. It happens due to state file mismatches or concurrent deployments trying to create the same repository name.

This error occurs during SSH port forwarding (tunneling) when the target service is not running, listening on the wrong port, or blocked by a firewall. The SSH connection succeeds, but the forwarded connection to the remote service fails.

This error occurs when Terraform cannot establish an HTTP connection, typically because the target server is unreachable or not listening. Common causes include uninitialized infrastructure, incorrect endpoints, or network connectivity issues.

Terraform restricts where ephemeral resource values can be used to prevent sensitive data from being stored in state files. This error occurs when you reference an ephemeral resource in a context that doesn't support ephemerality.

This error occurs when you reference an attribute that does not exist on a Terraform resource, data source, or module output. Common causes include typos in attribute names, missing .outputs in remote state references, and version incompatibilities.

You've reached the AWS NAT gateway quota (default 5 per Availability Zone). This occurs when provisioning infrastructure with Terraform and your account has too many NAT gateways in the same AZ or Deleting status gateways haven't fully cleaned up yet.

This error occurs when Terraform tries to access a list or map element using an index that doesn't exist. Common causes include accessing empty lists, using count with mismatched list sizes, or using incorrect index calculations.

Azure Storage Account names must be 3-24 characters using only lowercase letters and numbers, and must be globally unique. This error occurs when your Terraform configuration violates these naming rules.

The Terraform removed block requires a properly formatted resource address in the `from` argument. Common mistakes include using instance keys (like [0]), data sources, or quoted strings instead of bare resource references.

This error occurs when attempting to delete or recreate an AWS ECS cluster that still has active services. You must delete or deregister all services before the cluster can be deleted.

This error occurs when Terraform attempts to create an AWS Athena database that already exists in your AWS Glue Data Catalog. It typically happens due to case sensitivity mismatches or state synchronization issues between Terraform and AWS.

The SSH handshake failed error occurs when Terraform's remote-exec or file provisioner cannot establish a successful SSH connection to a remote host. This is typically due to authentication configuration issues, incorrect credentials, key type mismatches, or timing problems during instance initialization.

Terraform cannot write state to the configured backend and creates an errored.tfstate file. Common causes include permission issues, expired credentials, or backend conflicts. Use terraform state push to recover.

This error occurs when Terraform cannot access, locate, or properly resolve a filesystem path referenced in your configuration. It commonly happens with the file() function, module sources, or backend configurations when paths are incorrect, relative paths are misused, or files don't exist.

This error occurs when Terraform cannot locate authentication credentials for Terraform Cloud (app.terraform.io). The token must be configured in your CLI config file, environment variables, or interactive login to access remote backends and registries.

A precondition failed error occurs when a lifecycle precondition block evaluates to false in Terraform 1.2+. Fix it by reviewing the condition logic, input variables, and ensuring assumptions are met before applying.

A postcondition validation check in your Terraform configuration evaluated to false, blocking the apply operation. This typically indicates a resource doesn't meet expected criteria after creation.