All Errors

The 403 error when listing Azure service principals in Terraform occurs due to insufficient permissions on your service principal. This error typically happens when upgrading Azure provider versions or when your service principal lacks required Microsoft Graph API permissions.

This error occurs when Terraform cannot locate GCP credentials. Fix it by setting up Application Default Credentials with gcloud auth application-default login, setting the GOOGLE_APPLICATION_CREDENTIALS environment variable, or configuring credentials in your Terraform provider block.

The 'Required compute.instances.create permission' error occurs when your Terraform service account or user lacks the necessary IAM permissions to create Compute Engine VM instances on Google Cloud Platform. This happens when the identity used by Terraform doesn't have the compute.instances.create permission, typically because it's been granted an insufficient IAM role.

The 'No configuration files' error occurs when Terraform cannot find any .tf files in the working directory. This typically happens when you're in the wrong directory, your files lack the correct extension, or the workspace is misconfigured. Navigate to the correct directory containing your Terraform files to resolve it.

This error occurs in Terraform Enterprise/Cloud when the cost estimation service or Sentinel policy checker fails to enqueue jobs. Common causes include database schema issues after upgrades, network connectivity problems, or resource limitations.

This Terraform error occurs when you reference an attribute on the 'each' object that doesn't exist. The 'each' object only provides 'key' and 'value' attributes. Fix it by using the correct attribute or checking your for_each input structure.

This error occurs when a Terraform resource or module is missing a mandatory argument that the provider or module definition requires. Terraform will tell you exactly which argument is missing and which resource it applies to.

The .terraform.lock.hcl file has become out of sync with your provider requirements, typically due to platform differences or manual edits. This error prevents Terraform from proceeding until the lock file is regenerated or updated.

Terraform encountered an argument that the resource doesn't support. This typically happens due to provider version mismatches, typos in argument names, incorrect block nesting, or using arguments in the wrong resource type.

This error occurs when Terraform successfully creates a resource but cannot verify its existence immediately after. The provider creates the resource but fails to read it back, causing Terraform to believe the resource disappeared.

This error occurs when Terraform encounters a reference to a variable (using var.something) that has not been declared with a variable block. This commonly happens in dynamic blocks or resource configurations when you forget to define the input variable first.

This error occurs when Terraform's count argument depends on computed resource attributes that aren't known until after apply. The count value must be determinable during the plan phase to know how many resources to create.

The "Backend configuration block has changed" error occurs when Terraform detects a change in your backend configuration block. This can happen when migrating backends or due to detected differences. Resolve it by running terraform init with either -reconfigure or -migrate-state flags.

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.