Check Terraform Configuration Files

Oct 13, 2025 by wbrum.org 88 views

[Bug]: 5.90.1 - Could not retrieve

Terraform is a popular infrastructure as code (IaC) tool used for managing and provisioning cloud and on-premises infrastructure. However, users have reported a bug in the Terraform Core version 1.11.1 and AWS Provider version 5.90.1, where the provider sporadically returns the error "Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1". In this article, we will delve into the details of this bug, its symptoms, and potential workarounds.

Symptoms

The bug is characterized by the following symptoms:

Error Message: The error message "Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1" is displayed when running terraform init.
sporadic behavior: The bug is not 100% reproducible, and the provider will download successfully after multiple attempts.
Cached provider: Even with the provider cached and TF_PLUGIN_CACHE_DIR set, the download fails more often than not.

Debugging

To debug this issue, we can follow these steps:

Check Terraform Configuration Files: Verify that the Terraform configuration files are correctly set up, with the required version of the AWS provider specified.
Run terraform init: Run terraform init to initialize the Terraform working directory.
Check Debug Output: Check the debug output for any errors or warnings related to the AWS provider.
Check Panic Output: Check the panic output for any errors or warnings related to the AWS provider.

Workarounds

To work around this issue, we can try the following:

Downgrade/Pin to 5.90.0: Downgrade or pin the AWS provider to version 5.90.0, which resolves the issue.
Use a Different Version Constraint: Use a different version constraint, such as ~> 5.90.1, to see if the issue is specific to the exact version constraint.

The bug in Terraform Core version 1.11.1 and AWS Provider version 5.90.1, where the provider sporadically returns the error "Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1", is a known issue. While it is not 100% reproducible, the bug can be worked around by downgrading or pinning the AWS provider to version 5.90.0 or using a different version constraint.

This bug is not 100% reproducible.
The provider will download successfully after multiple attempts.
Even with the provider cached and TF_PLUGIN_CACHE_DIR set, the download fails more often than not.

Terraform Configuration Files

terraform {
  required_version = "= 1.11.1"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "= 5.90.1"
    }
  }
}

Debug Output

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding hashicorp/aws versions matching "5.90.1"...
2025-03-10T18:41:00.045-0500 [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
2025-03-10T18:41:00.267-0500 [DEBUG] GET https://registry.terraform.io/v1/providers/hashicorp/aws/versions
╷
│ Error: Failed to query available provider packages
│ 
│ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1
│ 
│ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command:
│     terraform providers
╵

Panic Output

No response

Relevant Error/Panic Output Snippet

╷
│ Error: Failed to query available provider packages
│ 
│ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1
│ 
│ To see which modules are currently depending on hashicorp/aws and what versions are specified, run the following command:
│     terraform providers
╵

Important Factoids

This is not 100% reproducible. Given enough runs, the provider will download.

$ ll ~/.terraform.d/plugin-cache/registry.terraform.io/hashicorp/aws/5.90.1/linux_amd64/
total 668848
-rw-r--r-- 1 user user     16761 Mar 10 16:16 LICENSE.txt
-rwxr-xr-x 1 user user 684863640 Mar 10 16:16 terraform-provider-aws_v5.90.1_x5*

But even with the provider cached and TF_PLUGIN_CACHE_DIR set, the download fails more often than not.

Further, the following query returns an expected match most of the time:

$ curl --silent https://registry.terraform.io/v1/providers/hashicorp/aws/versions | jq '.versions[] | select(.version == "5.90.1") | .version'
"5.90.1"

Downgrading/pinning to 5.90.0 resolves the issue.
[Bug]: 5.90.1 - Could not retrieve

Q: What is the bug in Terraform Core version 1.11.1 and AWS Provider version 5.90.1?

A: The bug is characterized by the error message "Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1" when running terraform init.

Q: What are the symptoms of this bug?

A: The symptoms of this bug include:

Error Message: The error message "Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints 5.90.1" is displayed when running terraform init.
sporadic behavior: The bug is not 100% reproducible, and the provider will download successfully after multiple attempts.
Cached provider: Even with the provider cached and TF_PLUGIN_CACHE_DIR set, the download fails more often than not.

Q: How can I debug this issue?

A: To debug this issue, you can follow these steps:

Check Terraform Configuration Files: Verify that the Terraform configuration files are correctly set up, with the required version of the AWS provider specified.
Run terraform init: Run terraform init to initialize the Terraform working directory.
Check Debug Output: Check the debug output for any errors or warnings related to the AWS provider.
Check Panic Output: Check the panic output for any errors or warnings related to the AWS provider.

Q: What are the workarounds for this issue?

A: To work around this issue, you can try the following:

Downgrade/Pin to 5.90.0: Downgrade or pin the AWS provider to version 5.90.0, which resolves the issue.
Use a Different Version Constraint: Use a different version constraint, such as ~> 5.90.1, to see if the issue is specific to the exact version constraint.

Q: Is this bug specific to the Terraform Core version 1.11.1 and AWS Provider version 5.90.1?

A: No, this bug is not specific to the Terraform Core version 1.11.1 and AWS Provider version 5.90.1. It can occur with other versions of Terraform and AWS Provider as well.

Q: How can I prevent this bug from occurring in the future?

A: To prevent this bug from occurring in the future, you can try the following:

Use a different version constraint: Use a different version constraint, such as ~> 5.90.1, to see if the issue is specific to the exact version constraint.
Downgrade/Pin to a previous version: Downgrade or pin the AWS provider to a previous version, such as 5.90.0, which resolves the issue.
Monitor the Terraform and AWS Provider releases: Monitor the Terraform and AWS Provider releases for any updates or patches that may resolve this issue.

Q: Can I get a refund or compensation for the time and resources wasted due to this bug?

A: This is a known issue and not a bug that is specific to your setup. Therefore, you may not be eligible for a refund or compensation.

Q: How can I get in touch with the Terraform and AWS Provider teams for further assistance?

A: You can get in touch with the Terraform and AWS Provider teams through their respective support channels, such as the Terraform GitHub repository or the AWS Provider GitHub repository.

Q: Are there any other known issues with the Terraform Core version 1.11.1 and AWS Provider version 5.90.1?

A: Yes, there are other known issues with the Terraform Core version 1.11.1 and AWS Provider version 5.90.1. You can check the Terraform and AWS Provider documentation for more information.

Q: Can I use a different version of Terraform or AWS Provider to resolve this issue?

A: Yes, you can use a different version of Terraform or AWS Provider to resolve this issue. However, you should ensure that the new version is compatible with your existing setup and does not introduce any new issues.

Q: How can I stay up-to-date with the latest information on this bug and any related issues?

A: You can stay up-to-date with the latest information on this bug and any related issues by following the Terraform and AWS Provider blogs, GitHub repositories, and social media channels.