Error map
Invalid AWS Region Terraform: Error: Invalid AWS Region: us-east-3 / Error: configuring Terraform AWS Provider: validating provider credentials: operation error STS: GetCallerIdentity
Terraform · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
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.
SQS: The specified queue does not exist (AWS.SimpleQueueService.NonExistentQueue / QueueDoesNotExist)
The queue URL/name doesn’t exist in that region/account, or it was deleted (recently deleted names are blocked for 60 seconds).
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.
LocationNotAvailableForResourceType / InvalidResourceLocation
The resource type isn’t offered in that region, or the resource already exists in a different region than the template says.
Terraform: Error: Failed to install provider — Error while installing hashicorp/aws v5.40.0: could not query provider registry / Get "https://releases.hashicorp.com/...": dial tcp: i/o timeout
Terraform found the provider version but couldn't download/verify the package.
Terraform: Error: No value for required variable — The root module input variable "region" is not set, and has no default value
A variable without a default wasn't supplied.
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.
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
The provider changed planned values between plan and apply (a provider bug), so Terraform aborts.
Terraform: Error: creating EC2 Instance: UnauthorizedOperation: You are not authorized to perform this operation. User: arn:aws:iam::123:user/ci is not authorized to perform: ec2:RunInstances
The IAM identity used by Terraform lacks a permission needed for that resource.
Terraform: Error: building AzureRM Client: obtaining subscription ID / Please run 'az login' to setup account
The AzureRM provider can't find Azure credentials or a subscription.
Two steps away (34)
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
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…
AWS S3: NoSuchKey / NoSuchBucket — The specified key/bucket does not exist
S3 found no object at that key (or no bucket with that name in the region/account you’re calling).
An error occurred (UnauthorizedOperation): You are not authorized to perform this operation. Encoded authorization failure message: ...
The IAM identity is missing an EC2 (or related) permission. The encoded message tells you exactly which action and resource were…
InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested
AWS has no free capacity for that instance type in that Availability Zone right now.
VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit
Your account’s On-Demand (or Spot) vCPU quota for that instance family and region is used up.
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
API Gateway: {"message": "Endpoint request timed out"} (504 after 29 seconds)
The backend (usually Lambda) didn’t respond within API Gateway’s integration timeout (29 seconds by default for REST APIs).
ACM certificate stuck in Pending validation
ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.
EC2 status check failed: Instance reachability check failed (1/2 checks passed)
AWS can reach the host, but the operating system inside the instance isn’t responding — kernel panic, full disk, broken network c…
ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded
Requests exceed the table’s (or index’s) provisioned read/write capacity, or one partition is hot.
ConditionalCheckFailedException: The conditional request failed
A write’s ConditionExpression evaluated to false, so DynamoDB didn’t perform it — often exactly as designed.
DynamoDB ValidationException: One or more parameter values were invalid: Missing the key pk in the item / The provided key element does not match the schema
The item or key doesn’t match the table’s primary key schema — wrong attribute name, wrong type, or missing sort key.
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
An Azure Resource Manager (ARM/Bicep/Terraform) deployment failed; the inner error under “details” has the real cause.
ResourceGroupNotFound: Resource group 'x' could not be found
The resource group doesn’t exist in the subscription the command or deployment is using.
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded)
Docker couldn’t reach the registry in time — a network, DNS, proxy or firewall problem between your machine and the registry.
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
Unable to connect to the server: dial tcp <ip>:443: i/o timeout
kubectl can’t reach the API server at all — network path, VPN, firewall or a private endpoint you’re outside of.
Terraform: Error: Missing required argument — The argument "ami" is required, but no definition was found
A resource/module block lacks an argument the schema requires.
Terraform: Error: Invalid value for variable — "instance_type" must be a t3 type / The given value is not suitable for var.x declared at variables.tf:1,1-17: string required
A variable value failed its type or `validation` block.
Terraform: Error: Invalid function argument — Invalid value for "list" parameter: list of string required / Call to function "lookup" failed
A built-in function got a wrong type/value (empty list, missing key, wrong type).
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: Inconsistent conditional result types — The true and false result expressions must have consistent types
A `cond ? a : b` expression returns values of different types/shapes.
Terraform: Error: Unsupported attribute — This object has no argument, nested block, or exported attribute named "foo"
An expression references an attribute that the resource/data source/module output doesn't expose.
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: 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).
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.
is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::...:role/...
The caller can’t assume the role — either its own policy doesn’t allow sts:AssumeRole, or the role’s trust policy doesn’t trust t…
Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server
The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
UnrecognizedClientException: The security token included in the request is invalid
The access key or session token isn’t recognised — wrong/deleted key, a session token missing for temporary credentials, or a reg…
AADSTS50020: User account from identity provider does not exist in tenant and cannot access the application
The signed-in user belongs to another tenant (or is a personal Microsoft account) and isn’t a guest in the app’s tenant.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError