All Errors

This error occurs when Terraform provider plugins crash or lose communication with Terraform Core. Usually caused by provider bugs, invalid configurations, or incompatible versions. Upgrading providers and checking logs typically resolves the issue.

This Terraform error occurs when you try to create an AWS Step Functions state machine with a name that already exists in your AWS account/region, but the resource isn't managed by your current Terraform state. Fix it by importing the existing resource or choosing a unique name.

The source address in a moved block cannot reference a resource that uses count or for_each. You must specify individual resource instances.

This error occurs when your Azure subscription has reached its resource quota limit for creating AKS clusters or provisioning the required vCPUs for nodes. Azure enforces quota limits per subscription and region to prevent unintended over-provisioning. Resolving this requires either requesting a quota increase or using fewer resources in your cluster configuration.

AWS Batch ClientException errors when creating job queues typically indicate compute environment issues, IAM permissions, or VPC configuration problems. This guide covers the most common causes and step-by-step fixes.

Resource creation cancelled occurs when Terraform interrupts or cancels the provisioning of a resource, either due to a dependent resource failure, user interruption, or context deadline. The state file may be left inconsistent with actual cloud resources.

This error occurs when Terraform cannot locate or access a remote module you're trying to use. Common causes include incorrect source paths, authentication issues, network connectivity problems, or missing initialization steps.

CloudFront AccessDenied errors occur when your AWS credentials lack required permissions. This guide covers IAM permission issues, S3 bucket policies for origins, and certificate permissions needed for successful distribution creation.

This error occurs when Terraform attempts to create an Azure SQL Database but cannot find the referenced SQL Server. It typically results from resource dependency issues, incorrect server references, or timing delays in Azure resource propagation.

The null_resource with provisioners is deprecated in modern Terraform. Upgrade to Terraform 1.4+ and use terraform_data instead, or migrate to native provider features for better reliability and maintainability.

The ClusterAlreadyExists error occurs when Terraform attempts to create a Redshift cluster with an identifier that already exists in your AWS account. Since cluster identifiers must be unique within an account and region, this error indicates the cluster was previously created or still exists from a failed operation.

This error occurs when trying to create an Azure Key Vault with a name that already exists, either as an active vault or in a soft-deleted state. Azure Key Vaults have globally unique names and are subject to soft-delete retention periods.

AWS WAF has account-level quotas on the number of WebACLs, rules, and other resources you can create. This error occurs when you exceed those limits. Resolve it by consolidating resources, removing unused WAF entities, or requesting quota increases.

Terraform's TLS certificate parsing error occurs when the TLS provider encounters malformed, expired, or untrusted certificates. This error typically appears when using data sources like tls_certificate or connecting to remote backends with problematic certificates.

Helm deployments often timeout when Kubernetes resources take longer than expected to reach their desired state. This error typically indicates insufficient cluster resources, slow image pulls, or misconfigured healthchecks that prevent pods from becoming ready.

This error occurs when Terraform cannot parse a timestamp string in RFC3339 format, commonly from AWS SSO credentials or invalid time provider usage. Fixing it involves updating credentials, correcting timestamp formats, or using the time provider correctly.

State migration fails when Terraform cannot automatically transfer state from an old backend to a new one. This typically occurs due to version mismatches, lock conflicts, permissions issues, or backend connectivity problems during terraform init -migrate-state.

Terragrunt shows this error when it cannot determine the specific exit code from an underlying command failure. The actual error is usually displayed before this message, making it crucial to look at the full error output to identify the root cause.

This warning appears when SSH detects that a remote server's host key has changed since you last connected to it. The offending key is stored in your known_hosts file, and SSH refuses to connect until you remove or update the old key entry.

A Terraform provisioner (local-exec or remote-exec) executed a command that failed with exit status 1. This occurs when the underlying script or command returns a non-zero exit code, causing the provisioner to fail and mark the resource as tainted.