All Errors

This error occurs when you try to include a non-string value (like a list or tuple) directly in a string template using ${} interpolation syntax. Use the join() function or remove unnecessary interpolation syntax to fix it.

This Terraform error occurs when you provide an incompatible type (like a string, number, or object) where a list of strings is expected. Fix it by understanding Terraform's type system and using the correct list syntax in your configuration.

The duplicate resource error occurs when Terraform detects two or more resources with the same resource address (type and name combination) in your configuration. This prevents Terraform from planning or applying your infrastructure changes.

This error occurs when Terraform encounters a function name it doesn't recognize. Common causes include version mismatches, deprecated functions, or using Terragrunt functions in Terraform code.

This error occurs when using 'terraform import', 'terraform state rm', or 'terraform state mv' with a resource address that doesn't exist in your Terraform configuration files. Terraform requires the resource to be defined (or at least have a placeholder) in your .tf files before you can manage it via state commands.

The LimitExceededException error occurs when you exceed AWS KMS quotas during Terraform apply. This typically happens when creating too many KMS keys or hitting request rate limits in a region. AWS KMS has default limits like 100,000 customer-managed keys per region and rate limits for cryptographic operations.

The InvalidChangeBatch error occurs when Route53 rejects your Terraform resource record set changes due to conflicts, validation issues, or mismatched values. This guide covers the most common causes and solutions.

This error occurs when a version constraint string in your Terraform configuration uses incorrect syntax. Version constraints appear in required_version, required_providers blocks, and module version fields. Common causes include malformed operators, missing version numbers, empty strings, and unsupported syntax. The fix involves using proper version constraint operators and format.

The remote-exec provisioner failed to execute scripts on a remote resource. This typically occurs due to connectivity issues, authentication failures, or timeout problems when Terraform tries to run commands over SSH or WinRM.

This error occurs when Terraform tries to access an element (using bracket notation) of a value that is null. It happens with data sources that return no results or when accessing resources created conditionally with count.

This error occurs when Terraform encounters a resource type it doesn't recognize. Common causes include missing provider configuration, typos in resource type names, or using an unsupported resource type with the current provider version.

This error occurs when you assign a value to a Terraform variable or argument that expects a map(string) type, but you're providing a map with non-string values (numbers, booleans, lists, etc.). Terraform requires all values in a map(string) to be strings, and automatically converting incompatible types fails validation.

The "InvalidParameterValueException" error occurs when creating AWS Lambda functions with Terraform due to invalid configuration parameters. Common causes include S3 bucket region mismatches, VPC permission issues, IAM role problems, or exceeding service quotas.

This error occurs when passing an argument to a module that either doesn't exist as a variable definition or has an incorrect type. Fix it by ensuring the module has the required variable declared and you're passing the correct data type.

Terraform cannot find a referenced provider alias because it wasn't defined in your root module configuration. This error occurs when using aliased providers with modules without proper configuration passing.

A deposed object occurs when Terraform's "create_before_destroy" lifecycle fails mid-operation, leaving the old resource stuck in state. This happens when resource creation succeeds but destruction fails, or operations are interrupted. Fix by running terraform apply again or manually cleaning up state.

Terraform fails to import resources when the same import block ID is used multiple times. This error prevents Terraform from processing import configurations that reference different modules or resources with the same ID value.

The Expected attribute terminator error occurs when Terraform's HCL parser encounters invalid syntax in a resource or block attribute definition. This typically happens due to missing commas, incorrect quotation marks, or improper line breaks. Fix it by reviewing your configuration syntax carefully using terraform validate.

The "defaults" function was removed in Terraform 1.3.0 as part of the optional attributes feature stabilization. This error occurs when using the deprecated function with newer Terraform versions. Replace it with native default value syntax in variable type definitions.

The "Moved block with ambiguous destination" error occurs when multiple moved blocks in your Terraform configuration target the same destination resource. Terraform cannot determine which source should be moved to that destination, creating ambiguity that prevents the refactoring from proceeding.