未找到 Terraform AWS Provider 的有效凭证来源

Question

我正在使用 shared_cred_file 作为 aws 提供商。以 aws provider 版本 3.63 为例，terraform 计划运行良好。

当我使用 aws provider 4.0 时，它会提示我使用 shared_credentials_files 的应用更改设置。修改后没有报错，但是第二个报错依旧

可能是什么问题？

Warning: Argument is deprecated
│
│   with provider[“registry.terraform.io/hashicorp/aws”],
│   on main.tf line 15, in provider “aws”:
│   15:   shared_credentials_file = “~/.aws/credentials”
│
│ Use shared_credentials_files instead.
│
│ (and one more similar warning elsewhere)
╵
╷
│ Error: error configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found.
│
│ Please see https://registry.terraform.io/providers/hashicorp/aws
│ for more information about providing credentials.
│
│ Error: no EC2 IMDS role found, operation error ec2imds: GetMetadata, canceled, context deadline exceeded
│
│
│   with provider[“registry.terraform.io/hashicorp/aws”],
│   on main.tf line 13, in provider “aws”:
│   13: provider “aws” {
│

///////////////////////////////
// Infrastructure init
terraform {
  backend "s3" {
    bucket                  = "monitoring-********-infrastructure"
    key                     = "tfstates/********-non-prod-rds-info.tfstate"
    profile                 = "test-prof"
    region                  = "eu-west-2"
    shared_credentials_file = "~/.aws/credentials"
  }
}

    provider "aws" {
      profile                 = "test-prof"
      shared_credentials_files = ["~/.aws/credentials"]
      region                  = "eu-west-2"
    }

    Error: error configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found.
        │
        │ Please see https://registry.terraform.io/providers/hashicorp/aws
        │ for more information about providing credentials.
        │
        │ Error: no EC2 IMDS role found, operation error ec2imds: GetMetadata, canceled, context deadline exceeded
        │
        │
        │   with provider["registry.terraform.io/hashicorp/aws"],
        │   on main.tf line 13, in provider "aws":
        │   13: provider "aws" {

cat 配置

[test-prof]
output = json
region = eu-west-2

cat 凭据

[test-prof]
aws_access_key_id = ****************
aws_secret_access_key = ******************

Answer 1

改变

provider "aws" {
  shared_credentials_file = "$HOME/.aws/credentials"
  profile                 = "default"
  region                  = "us-east-1"
}

至

provider "aws" {
  shared_credentials_file = "/Users/me/.aws/credentials"
  profile                 = "default"
  region                  = "us-east-1"
}

对我有用。

Answer 2

从版本 3 -> 4 迁移 AWS Provider 后，我们在管道中遇到了这个问题。

因此，对于任何使用 Azure DevOps 或任何其他 CI 工具的人来说，修复应该就像在管道中添加新步骤并创建共享凭据文件一样简单：

mkdir $HOME/.aws

echo [default] >> $HOME/.aws/credentials
echo aws_access_key_id = ${AWS_ACCESS_KEY_ID} >> $HOME/.aws/credentials
echo aws_secret_access_key = ${AWS_SECRET_ACCESS_KEY} >> $HOME/.aws/credentials

AWS_ACCESS_KEY_ID 和 AWS_SECRET_ACCESS_KEY 应该在您的管道中定义为 var 或 secrets。

Answer 3

根据最新的 Terraform 文档，它是这样工作的，

provider "aws" {
  region                    = "us-east-1"
  shared_credentials_files  = ["C:/Users/tf_user/.aws/credentials"]
  profile                   = "customprofile"
}

我遇到了同样的问题，这个东西对我有用。

未找到 Terraform AWS Provider 的有效凭证来源

no valid credential sources for Terraform AWS Provider found

amazon-web-services

terraform

credentials