All Errors

The ResourceAlreadyExistsException error occurs when Terraform tries to create an AWS CloudWatch Log Group that already exists. This commonly happens with Lambda functions that auto-create log groups, or when log groups were created outside Terraform.

The 'Invalid index' error occurs when Terraform tries to access an element in a list, tuple, or map using an index or key that doesn't exist. This commonly happens with empty collections, out-of-bounds array access, or missing map keys. The fix involves checking collection bounds, using conditional expressions, or applying the try() function.

This error occurs when AWS lacks sufficient On-Demand capacity to provision your requested EC2 instance type in the chosen Availability Zone. Capacity constraints are usually temporary and can be resolved by trying different AZs, instance types, or retrying after a few minutes.

The QueueNameExists error occurs when Terraform attempts to create an SQS queue with a name that already exists in your AWS account and region. SQS queue names must be unique within each account and region, so this error indicates either a previous queue creation, a recent deletion that is still cached, or a naming conflict with another service.

The map() function has been deprecated in Terraform v0.12 and removed in later versions. This error occurs when you use the legacy map() function syntax, which is no longer available. Replace deprecated map() calls with native map literal syntax using curly braces {}.

This error occurs when trying to delete a Terraform resource that has other resources depending on it. Terraform prevents this to maintain infrastructure consistency. You need to identify and delete dependent resources first or restructure your configuration.

Terraform raises a duplicate variable declaration error when the same variable is defined multiple times within a module. This prevents Terraform from validating and executing your configuration because variable names must be unique.

The 'Cannot import non-existent remote object' error occurs when terraform import attempts to import a resource that doesn't exist in the remote provider. This typically happens due to incorrect resource IDs, resources being deleted before import, or misconfigured provider credentials. Resolving this requires verifying the resource exists and using the correct import ID format.

The setsubtract function is not available in your Terraform version. This function computes the relative complement of two sets and was introduced in Terraform 0.12.20. Upgrading Terraform or using an older module version will resolve this error.

When Terraform Cloud or Enterprise fails to queue a run with "Failed to request run", the issue typically stems from API connectivity problems, network timeouts, or authentication failures. Troubleshooting requires verifying API access and identifying the underlying cause.

This networking error occurs when Terraform cannot establish a connection to a cloud provider, registry, or remote resource. It typically indicates DNS resolution failures, network connectivity issues, or security group/firewall restrictions blocking the required ports.

Terraform state write failures occur when Terraform cannot persist state changes to your backend storage due to permission issues, backend misconfiguration, or serial number conflicts. This prevents infrastructure changes from being recorded and can leave your state in an inconsistent state.

The replace_triggered_by lifecycle argument is invalid because it references a variable, data source, or non-existent resource. This argument only accepts managed resource references and was introduced in Terraform 1.2.

Terraform cannot read a file due to incorrect path, missing file, or permission issues. This typically occurs when using the file() function or reading configuration files with relative paths that aren't resolved correctly.

Terraform's lifecycle meta-argument only accepts valid arguments like create_before_destroy, prevent_destroy, ignore_changes, precondition, and postcondition. This error occurs when you use an unsupported argument name or incorrect syntax in the lifecycle block.

The aws_lambda_function resource requires mutually exclusive code deployment options. You cannot use both filename and image_uri in the same Lambda function—choose one based on whether you're deploying from a local file, S3, or container image.

This error occurs when Terraform's SSH client cannot authenticate with a remote server during provisioner operations. It typically indicates missing or misconfigured authentication credentials (private key, password, or SSH agent).

This error occurs when Terraform's fileset() function receives a malformed glob pattern. Terraform glob patterns follow POSIX syntax, and certain pattern combinations are invalid or unsupported, causing the configuration parsing to fail.

Terraform Cloud requires that an organization be specified in your cloud block configuration. This error occurs when you haven't configured which Terraform Cloud organization your infrastructure belongs to.

The Terraform AWS provider throws a conflicting configuration error when both the deprecated cpu_core_count argument and the newer cpu_options block are present in the same aws_instance resource. This conflict occurs because these are two incompatible ways of specifying the same CPU configuration, with cpu_core_count being deprecated in favor of cpu_options.