Error map
Provider produced invalid plan / inconsistent final plan Terraform: Error: Provider produced invalid plan — provider produced an invalid plan for aws_x.y, but we are tolerating it because it is using the legacy plugin SDK
Terraform · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
Terraform: Error: Your query returned no results. Please change your search criteria and try again.
A data source (e.g. `aws_ami`, `aws_vpc`) found nothing matching its filters.
Terraform: Error: Invalid AWS Region: us-east-3 / Error: configuring Terraform AWS Provider: validating provider credentials: operation error STS: GetCallerIdentity
The `region` is invalid/unavailable, or the provider can't reach AWS endpoints to validate credentials.
Terraform: Error: Invalid for_each argument — The "for_each" map includes keys derived from resource attributes that cannot be determined until apply
`for_each` keys depend on values only known after apply, so Terraform can't plan which instances exist.
Terraform: Error: Invalid count argument — The "count" value depends on resource attributes that cannot be determined until apply
`count` depends on something unknown at plan time, so Terraform can't decide how many instances to create.
Terraform: Error: Provider produced inconsistent result after apply — When applying changes to aws_x.y, provider produced an unexpected new value: Root resource was present, but now absent
After creating/updating a resource, the provider returned values that don't match what Terraform planned — usually a provider bug…
Terraform: Error: No valid credential sources found — failed to refresh cached credentials, no EC2 IMDS role found / Error: configuring Terraform AWS Provider: no valid credential sources
The AWS provider found no credentials (env vars, shared config, SSO, role, instance profile).
Terraform: Error: Saved plan is stale — The given plan file can no longer be applied because the state was changed by another operation after the plan was created
The state changed between `terraform plan -out` and `terraform apply planfile`.
Two steps away (17)
InvalidAMIID.NotFound: The image id '[ami-xxxx]' does not exist
The AMI ID isn’t available in this region/account — AMI IDs are regional and private AMIs must be shared.
Terraform: Error: Reference to undeclared resource / Reference to undeclared input variable
The configuration refers to a resource, data source, variable or module output that isn’t declared in this module.
Terraform: Error: Invalid index — The given key does not identify an element in this collection value
You indexed a map/list/set with a key or position that doesn't exist.
S3 PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint
The request went to the wrong S3 region/endpoint for that bucket.
InvalidKeyPair.NotFound: The key pair 'x' does not exist
The key pair name you passed doesn’t exist in that region (key pairs are regional).
DynamoDB ResourceNotFoundException: Requested resource not found (table)
The table (or index) doesn’t exist in the region/account the client is using.
Terraform: Error: Cycle: aws_security_group.a, aws_security_group.b
Resources reference each other (directly or indirectly), so Terraform can't order them.
Terraform: Error: Output refers to sensitive values — a root module output containing sensitive data must be explicitly marked as sensitive
An output (or module output) exposes a value derived from a sensitive variable/attribute without `sensitive = true`.
Error from server (AlreadyExists): ... already exists
kubectl create tried to make an object whose name is already taken in that namespace.
The Deployment is invalid: spec.selector: Invalid value: field is immutable
You tried to change a field Kubernetes doesn’t allow to change after creation — Deployment selectors, Job templates, Service clus…
Terraform: Error: creating S3 Bucket (my-bucket): BucketAlreadyOwnedByYou / EntityAlreadyExists: Role with name x already exists
The resource exists outside Terraform's state (created manually or by another stack), so create fails.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: Unable to locate credentials / Could not load credentials from any providers
The AWS CLI/SDK found no credentials in any place it looks — env vars, profile files, SSO cache or an instance/task role.
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
CloudFormation: No updates are to be performed
You ran an update/deploy with a template and parameters identical to what’s deployed, so there’s nothing to change.
toomanyrequests: You have reached your pull rate limit (Docker Hub)
Docker Hub limits anonymous and free pulls; your IP or account has used its quota for the current window.
the input device is not a TTY
docker run/exec was called with -t (allocate a terminal) in a context with no terminal — CI, cron, a pipe or a script.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError