All Errors

The BucketAlreadyExists error occurs when Terraform attempts to create an S3 bucket that already exists in AWS. Since S3 bucket names are globally unique across all AWS accounts, this error indicates either the bucket was previously created, or another account owns that name.

A circular dependency occurs when two or more AWS security groups reference each other in their ingress/egress rules. Terraform cannot determine creation order, causing the plan to fail. The fix is to separate security group rules into aws_security_group_rule resources.

Terraform detected a circular dependency in your configuration where resources depend on each other in a way that creates an unresolvable loop. This breaks Terraform's directed acyclic graph requirement for determining resource creation order.

Terraform encounters shared memory exhaustion, typically in Terraform Enterprise with PostgreSQL backends. This occurs when the system's IPC shared memory is insufficient for the database operations.

The "Invalid data source" error occurs when Terraform cannot find or recognize a data source in your configuration. This typically happens due to typos in the data source type, missing provider initialization, or using a data source that is not supported by your provider version.

This error occurs when a Terraform function receives an argument with an incompatible type or incorrect number of parameters. Common causes include type mismatches, missing files, or using the wrong function syntax.

This error occurs when Terraform cannot find a provider in the Terraform Registry. Common causes include incorrect provider source syntax, network connectivity issues, or missing required_providers declarations.

This error occurs when Terraform cannot establish a connection to registry.terraform.io to download provider packages during 'terraform init'. It typically results from network issues, DNS resolution problems, proxy misconfiguration, or firewall restrictions.

Terraform Enterprise returns a 503 error with 'Please wait while outputs are parsed' when the API is still processing state version outputs. This typically requires retry logic and occurs during high-volume state operations.

Terraform requires explicit backend reinitialization when backend configuration changes to prevent state corruption. This error occurs after modifying, removing, or switching backend configurations.

This error occurs when Terraform cannot find the provider configuration for a resource. It typically happens when a provider block is missing, incorrectly defined, or the provider hasn't been initialized in the working directory.

This error occurs when Terraform detects a mismatch between what a provider planned to do during the plan phase and what it actually did during apply. This typically indicates a provider bug, race condition, or computed value inconsistency.

This error occurs when Terraform cannot retrieve provider packages from the registry due to network issues, version constraint mismatches, or authentication problems. Resolving it typically involves checking connectivity, updating version constraints, or using the -upgrade flag.

The "Invalid expression" error in Terraform occurs when the HCL parser encounters malformed syntax in your configuration. This is typically caused by incorrect interpolation syntax, missing or extra brackets, or incomplete expressions.

Context deadline exceeded occurs when a Terraform provider API call times out before receiving a response. This typically indicates the client timeout is shorter than the API operation duration, particularly common with large cloud resource deployments.

This error occurs when Terraform detects a mismatch between your module version constraints and the currently locked versions. It happens when you update version requirements in your module declarations without updating the .terraform.lock.hcl file.

The 'Error: Unauthorized' in Terraform occurs when authentication credentials are missing, expired, or invalid when communicating with cloud APIs or Kubernetes clusters. This commonly happens with token-based authentication that expires between operations.

This error occurs when Terraform detects a symlink with an absolute path target in your configuration or module sources during remote execution. Terraform's unpacking mechanism only allows relative symlinks to prevent security issues and portability problems.

Terraform cannot find valid AWS credentials to authenticate with the AWS Provider. This occurs when credentials are not configured via environment variables, AWS CLI credentials file, IAM roles, or provider settings.

This error occurs when Terraform's provider returns unexpected values after applying changes, often leaving resources created but untracked in state. It's typically a provider bug related to eventual consistency in cloud APIs.