All Errors

The AlreadyExistsException error occurs when Terraform tries to create an AWS Backup Plan that already exists in your AWS account. This happens when the resource exists outside of Terraform state or wasn't properly imported.

Terraform's NotFoundException error when creating API Gateway resources typically occurs when you're trying to reference a REST API that doesn't exist yet, have missing dependencies, or are experiencing a race condition. Resolve it by adding explicit dependencies, using proper resource references, and ensuring your state is synchronized.

Terraform test assertions fail when conditions evaluate to false during test execution. This prevents test files from passing and indicates mismatched expected vs actual values in your test configuration.

The Terraform element() function fails when applied to empty lists or tuples. This error commonly occurs when conditional logic causes data sources or resource counts to return zero results.

This error occurs when Terraform attempts to create a CodeBuild project that already exists in your AWS account. It typically happens when there's a mismatch between Terraform state and actual AWS resources.

This error occurs when AWS Kinesis exceeds account-level or shard-level limits. Common causes include reaching maximum concurrent stream creation, shard quota limits, or API rate limits. Resolving it requires requesting quota increases, optimizing stream configuration, or adjusting Terraform parallelism.

The NamespaceAlreadyExists error occurs when you attempt to create an Azure Service Bus namespace with a name that's already in use. Service Bus namespace names must be globally unique across all Azure subscriptions. Resolve this by using a different namespace name, checking for soft-deleted resources, or importing the existing namespace into your Terraform state.

This error occurs when a Terraform configuration requires an input variable but no value is provided for it. Terraform needs variable values supplied via -var flags, .tfvars files, environment variables, or default values in the variable declaration.

This error occurs when attempting to create an Azure Container Registry (ACR) that already exists in Azure. The registry name must be globally unique across all Azure subscriptions. This typically happens when the resource was previously created outside Terraform or when Terraform state is lost. The fix involves checking if the resource exists, importing it into state, using unique names, or properly managing Terraform backend state.

Elastic Beanstalk returns InvalidParameterValue errors when environment parameters are invalid, outdated solution stacks are used, or the environment is in a non-ready state. This commonly occurs with Terraform when resource configurations conflict or provider versions mismatch.

The "No source for module" error occurs when Terraform cannot locate the module source you specified. This happens when the module path is missing, incorrect, or the modules have not been initialized. Resolving this requires verifying the source path and running terraform init.

The AddressSpaceOverlap error occurs when you attempt to create or peer Azure Virtual Networks (VNets) with overlapping CIDR address ranges. Azure requires all VNets and subnets to have non-overlapping IP address spaces.

This error occurs when for_each tries to iterate over resource attributes that are not known until apply time. Terraform requires all for_each keys to be known during the planning phase to predict resource creation.

This error occurs when Terraform attempts to create an AWS ECR repository that already exists. It happens due to state file mismatches or concurrent deployments trying to create the same repository name.

This error occurs during SSH port forwarding (tunneling) when the target service is not running, listening on the wrong port, or blocked by a firewall. The SSH connection succeeds, but the forwarded connection to the remote service fails.

This error occurs when Terraform cannot establish an HTTP connection, typically because the target server is unreachable or not listening. Common causes include uninitialized infrastructure, incorrect endpoints, or network connectivity issues.

Terraform restricts where ephemeral resource values can be used to prevent sensitive data from being stored in state files. This error occurs when you reference an ephemeral resource in a context that doesn't support ephemerality.

This error occurs when you reference an attribute that does not exist on a Terraform resource, data source, or module output. Common causes include typos in attribute names, missing .outputs in remote state references, and version incompatibilities.

You've reached the AWS NAT gateway quota (default 5 per Availability Zone). This occurs when provisioning infrastructure with Terraform and your account has too many NAT gateways in the same AZ or Deleting status gateways haven't fully cleaned up yet.

This error occurs when Terraform tries to access a list or map element using an index that doesn't exist. Common causes include accessing empty lists, using count with mismatched list sizes, or using incorrect index calculations.