All Errors

This error occurs when Terraform encounters an unsupported character in your HCL configuration file. Common causes include special characters in identifiers, copy-pasted curly quotes, hidden Unicode characters, or encoding issues.

Terraform state becomes inconsistent when resources_processed flag stays false after operations. This typically occurs due to state lock issues, interrupted operations, or provider problems that leave the state file in an incomplete state.

This error occurs when a Terraform provider plugin crashes or fails to communicate via gRPC. It typically indicates the provider encountered an unhandled error and stopped responding to Terraform.

This error occurs when Terraform attempts to launch an EC2 instance using an AMI ID that doesn't exist in the specified AWS region. The most common cause is using an AMI ID from a different region, as AMI IDs are region-specific.

The 'unsupported attribute' error occurs when you reference an attribute that doesn't exist on a Terraform resource, nested block, or data source. This typically happens due to typos in attribute names, incorrect syntax between arguments and blocks, provider version mismatches, or using deprecated attributes that have been removed or renamed.

This error occurs when Terraform detects that a resource is in a degraded or incomplete state and must be destroyed and recreated. Learn how to handle tainted resources and fix this issue.

Terraform cannot find valid AWS credentials to authenticate with AWS. This happens when credentials are not configured via environment variables, shared credentials file, IAM roles, or provider configuration.

The 'Missing resource instance key' error occurs when you try to access attributes of a resource that has for_each set without specifying which instance to access. Fix it by using specific instance keys like aws_instance.example[each.key].id or using a for expression in outputs.

This error occurs when Terraform tries to reference a module that hasn't been declared in the current configuration scope. Learn how to properly declare modules and pass values between them.

Terraform state lock errors occur when Terraform cannot acquire an exclusive lock on your state file, usually due to concurrent operations, stale locks, or hung processes. This error prevents infrastructure changes and requires identifying and releasing the conflicting lock.

This error occurs when Terraform cannot acquire a lock on your Azure Blob Storage state file because another process or operation already holds the lock. It typically happens when multiple pipelines run concurrently or when a previous operation terminated unexpectedly.

The Terraform AWS provider plugin crashes during plan or apply operations. This is typically caused by version-specific bugs, memory constraints, or problematic resource configurations. Most cases are resolved by upgrading to a patched provider version or downgrading to a stable release.

The InvalidParameterCombination error occurs when your Terraform aws_db_instance configuration contains incompatible parameter values. This error is caused by mismatches between the database engine, instance class, storage settings, or other parameters. Resolving it requires identifying which parameters conflict and updating your configuration.

This error occurs when Terraform cannot access your S3 bucket used for remote state storage. It typically results from missing IAM permissions, incorrect AWS credentials, or misconfigured backend settings.

This Terraform error occurs when your configuration references a variable using var.variable_name syntax, but the variable hasn't been declared. Fix it by adding the missing variable block to your Terraform code.

The EntityAlreadyExists error occurs when Terraform attempts to create an IAM Role that already exists in AWS. This typically happens when the resource exists in AWS but is missing from your Terraform state file. Resolve it by importing the existing role, deleting it from AWS and recreating it, or checking for state file mismatches.

This error occurs when Terraform tries to delete an S3 bucket that still contains objects. By default, Terraform prevents bucket deletion to protect against accidental data loss. The fix is to enable force_destroy in your aws_s3_bucket resource or manually delete objects first.

The "unknown certificate issuer" error occurs when Terraform cannot verify the SSL/TLS certificate of a remote endpoint because the certificate was signed by an untrusted or unrecognized Certificate Authority. This commonly happens with self-signed certificates, corporate proxies, or custom registries.

This error occurs when Terraform can't locate a resource that exists in your state file but has been deleted manually or moved outside of Terraform. Fix it by syncing your state file with actual infrastructure using terraform refresh, terraform import, or terraform state commands.

This error occurs when apt cannot verify GPG signatures for package repositories because a required GPG key is missing, expired, or outdated. It prevents package updates and installations.