Terraform Tutorial — Provider Errors

1 minute read

Provider errors typically occur during terraform init when Terraform can’t download or configure the required providers.


Error: Failed to Install Provider

Error: Failed to install provider

Could not find required providers:
  registry.terraform.io/hashicorp/aws: no available releases match
  the given constraints ~> 99.0

Cause: The version constraint doesn’t match any available version.

Fix: Check registry.terraform.io for valid versions:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"    # fix the version constraint
    }
  }
}

Error: Incompatible Provider Version

Error: Incompatible provider version

Provider "hashicorp/aws" v4.67.0 does not support resource type
"aws_bedrockagent_agent".

Cause: The resource you’re using was added in a newer provider version.

Fix:

# Upgrade to the latest provider
$ terraform init -upgrade

Or update the version constraint:

required_providers {
  aws = {
    source  = "hashicorp/aws"
    version = "~> 5.30"   # newer version
  }
}

Error: Lock File Mismatch

Error: Failed to install providers

Terraform has been configured to lock provider versions.
The selected provider was not found in the lock file.

Cause: .terraform.lock.hcl doesn’t match the required providers.

Fix:

# Update the lock file
$ terraform init -upgrade

Error: Provider Not Found

Error: Invalid provider registry host

The host "registry.terrafrom.io" was not found.

Cause: Typo in the provider source.

Fix: Check for typos:

# Wrong
source = "hashicorp/awss"

# Right
source = "hashicorp/aws"

What’s Next?

Let’s handle state drift — when real infrastructure doesn’t match state.


← Credential Errors State Drift and Conflicts →