All Errors

The prevent_destroy lifecycle argument protects critical resources from accidental deletion. When enabled, Terraform blocks any destroy operations. To proceed, you must either remove the protect_destroy setting, delete the resource from configuration, or remove it from Terraform state.

Your AWS account has hit the limit for security groups in a VPC or region. This happens when creating too many security groups or when Terraform state becomes out of sync with AWS. You can request a limit increase, consolidate security groups, or clean up unused resources.

This error occurs when Terraform attempts to parse JSON configuration but encounters an unexpected character. It's commonly caused by syntax errors in JSON files, invalid file encoding, or corrupted data containing special characters.

The AccessDenied error when creating an IAM Role in Terraform means your AWS credentials lack the required iam:CreateRole permission. This can be caused by insufficient IAM permissions, permission boundaries, service control policies (SCPs), or missing trust policies. Resolve it by granting the necessary IAM permissions or adjusting your policy boundaries.

This error occurs when Terraform lacks the necessary IAM permissions to create or manage SNS topics in AWS. Fix it by ensuring your IAM user or role has sns:CreateTopic and sns:SetTopicAttributes permissions.

The Invalid value for input variable error occurs when you pass a value that doesn't match the expected type or fails validation rules defined for a Terraform input variable. Fix it by ensuring your values match the variable's type constraints and any custom validation conditions.

Terraform rejects null values in lists because they create ambiguity in configuration. This error typically occurs with conditional expressions or data source outputs. Use Terraform's built-in functions like compact() or filtering expressions to remove nulls before passing them to list arguments.

This Terraform provider error indicates that a resource attribute was modified by the provider during planning without being marked as 'Computed' in the schema. The issue is a provider bug where attributes are set to non-null values without the proper schema configuration. This typically affects attributes with Optional: true and Default set, and is resolved by updating the provider or reporting the issue to the provider maintainers.

This error occurs when Terraform receives a value of the wrong type for an argument. It commonly happens when passing a list where a string is expected, or wrapping already-typed values in extra brackets.

You've reached your AWS account's vCPU quota limit for EC2 instances. AWS enforces soft limits on the number of vCPUs you can use in a region. This error occurs when trying to launch an instance that would exceed your current quota.

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.