All Errors

The local-exec provisioner error occurs when Terraform fails to execute a local command on the machine running Terraform. Common causes include missing commands in PATH, non-zero exit codes, permission issues, or working directory problems. Debugging requires checking command availability, exit codes, and execution environment.

The "Unsupported state file format" error occurs when Terraform cannot read your state file, typically because it was created by a newer Terraform version. Resolve this by upgrading Terraform or restoring state from a backup.

Terraform dynamic blocks require a 'content' block to define the attributes of generated nested blocks. This error occurs when the content block is missing, incorrectly named, or when you try to pass data directly without the required content wrapper.

This error occurs when a Terraform function receives an argument with an invalid value or type. Learn how to identify the problematic parameter and fix type mismatches, null values, and invalid function calls.

This error occurs when you try to use Terraform template directives (like %{for}, %{if}) inside a dynamic block. Dynamic blocks use their own for_each iteration mechanism and don't support template syntax. The fix is to remove template directives and use dynamic block expressions instead.

Terraform resource configuration often has mutually exclusive arguments where you must choose one option or another, not both. This error occurs when you try to use conflicting options simultaneously in your Terraform code.

This error occurs when Terraform encounters a value with the wrong type in a context that requires a number. Common causes include using strings or booleans where numbers are expected, particularly in count expressions, arithmetic operations, or module arguments.

AWS ACM limits the number of certificates you can request per year. This error occurs when you exceed your account's certificate quota or domain limit. Resolve it by requesting a quota increase or reusing existing certificates.

The VpcLimitExceeded error occurs when your AWS account has reached the maximum number of VPCs allowed per region (default: 5). Resolve this by deleting unused VPCs or requesting a quota increase from AWS Service Quotas.

This error occurs when using Terraform JSON configuration files (.tf.json) with property names that don't match valid arguments or block types for the resource or block being configured. The error indicates an unrecognized attribute.

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.