All Errors

The ResourceInUseException error occurs when Terraform attempts to create an EKS cluster with a name that already exists in your AWS account, or when cluster resources are still being deleted. This prevents the cluster creation from proceeding until the conflicting resource is resolved.

This error occurs when Terraform cannot find a provider version that satisfies all version constraints in your configuration and modules. Conflicting constraints between modules or outdated local plugins typically cause this issue.

A local value in Terraform is referencing itself, either directly or through a chain of other locals. Terraform cannot evaluate self-referential or circular dependency chains. This error is resolved by breaking the circular reference and restructuring your locals so dependencies flow in one direction.

Terraform 0.13+ deprecated specifying provider versions in the provider block. Move version constraints to the required_providers block in your terraform configuration to fix this warning.

This error occurs when Terraform attempts to create an Elastic Load Balancer that already exists in AWS, usually due to state file mismatches or resource replacement ordering issues. The load balancer may exist in AWS but not be tracked in your Terraform state.

This error occurs when Terraform tries to select or use a workspace that doesn't exist in your current backend. You can fix it by creating the workspace first or using the auto-create flag in newer Terraform versions.

This error occurs when you attempt to use a Terraform state file that was created with a newer version of Terraform than the one you're currently running. Terraform state files are forward compatible but not backward compatible, preventing downgrade scenarios.

This error occurs when trying to modify an RDS instance but the VPC or subnet configuration is in an incompatible state. Common causes include missing subnets, insufficient IP addresses, or disabled DNS settings.

This error occurs when an output block is placed in an invalid location within your Terraform configuration. Output blocks must be defined at the root level of your Terraform files, not nested inside resource, data, module, or other configuration blocks.

This error occurs when Terraform attempts to create an AWS Secrets Manager secret with a name that already exists or is marked for deletion. AWS keeps deleted secrets in a recovery window (default 30 days) during which the name cannot be reused.

The "No Space Left on Device" error occurs when Terraform runs out of disk space during initialization, planning, or apply operations. This typically happens in CI/CD environments or when provider caches grow too large. Diagnose disk usage and implement caching strategies to resolve.

Terraform import fails when credentials aren't configured locally. Unlike other Terraform commands that run in the cloud, terraform import executes on your workstation and requires local authentication to access cloud resources.

This error occurs when Terraform tries to create a GCP resource (like Dataflow jobs) but the required API hasn't been enabled in your Google Cloud project. The fix is to explicitly enable the API using the google_project_service resource in Terraform or via gcloud CLI.

This error occurs when Terraform's Azure provider fails to authenticate with the Resource Manager API. It typically happens due to missing Azure CLI, authentication issues, or configuration problems with OIDC or service principal credentials.

When using Terraform with Google Cloud Platform, you may encounter a 409 error stating 'The resource already exists' when trying to create or update SSL certificates. This typically occurs when the certificate wasn't properly deleted after a previous operation, or when using create_before_destroy lifecycle rules with managed certificates.

This error occurs when the Terraform Azure provider attempts to use an API version that doesn't exist or isn't registered in your subscription. It typically indicates either resource provider registration issues, API version mismatch, or regional API support limitations.

The Cloud Resource Manager API disabled error occurs when Terraform tries to manage GCP resources but the cloudresourcemanager.googleapis.com API has not been enabled on the project. This is a chicken-and-egg problem where the API must be manually enabled before Terraform can use it.

The "InUseRouteTableCannotBeDeleted" error occurs when Terraform tries to delete an Azure route table that is still associated with a subnet. Azure prevents deletion of route tables that are actively in use, requiring proper disassociation before removal.

The "Invalid for_each argument" error occurs when Terraform cannot determine the keys in a for_each loop before applying the plan. This typically happens when the for_each value depends on computed resources or unknown attributes that haven't been created yet.

The ResourceDependencyException error occurs when Terraform tries to delete AWS Image Builder Components or Recipes that have dependent resources (like Image Pipelines) still referencing them. Terraform attempts to delete resources in the wrong order, causing AWS to reject the deletion. You must manually manage the deletion order or use workarounds.