All Errors

The "Saved plan is stale" error occurs when Terraform detects that the state file has changed after you created a plan but before applying it. This typically happens in CI/CD pipelines or when multiple operations modify the state concurrently.

Terraform cannot read your terraform.tfvars file due to syntax errors, missing variable declarations, file naming issues, or incorrect file paths. Fix the tfvars file syntax and ensure variables are declared in your .tf files.

This error occurs when Terraform cannot read a file due to insufficient file system permissions. Common causes include restrictive file permissions on local files, provider binary permission issues, or permission changes during Terraform operations.

Terraform plan failed with a generic error message indicating one or more problems with your configuration. This error requires looking at the detailed error message that follows to identify the actual issue, which could be syntax errors, invalid resource configurations, or provider problems.

The DynamoDB ResourceInUseException error occurs when Terraform attempts to create a table that already exists or is in a transitional state. This happens when a table with the same name already exists in your AWS account, or the table is currently being modified. Most cases are resolved by importing the existing table into Terraform state or using a different table name.

The InvalidSubnet.Range error occurs when your Terraform subnet CIDR block is invalid or doesn't fit within your VPC's IP address space. This typically happens when the subnet CIDR is outside the VPC range, overlaps with existing subnets, or when using secondary CIDR blocks before they're fully associated.

State refresh failures occur when Terraform can't synchronize with remote infrastructure due to state locks, connectivity issues, or resource changes. This guide covers diagnosis and recovery strategies for different root causes.

The EBS VolumeLimitExceeded error occurs when you've reached AWS account or regional limits for EBS volumes. This can be resolved by deleting unused volumes or requesting a service quota increase through AWS.

The "Value for undeclared variable" warning occurs when you provide a value for a variable that has not been declared in your Terraform configuration. Fix it by adding a variable block to declare the variable or removing the unused value assignment.

This error occurs when you define multiple provider blocks for the same provider without using distinct aliases. Each provider configuration after the first must have a unique alias to distinguish between them.

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.