-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: NoCredentialProviders: no valid providers in chain. Deprecated. │ For verbose messaging see aws.Config.CredentialsChainVerboseErrors │ #1
Comments
Any update on this? We're also running into the same problem. |
The |
in my case the error was in the region settings of the ct_home_region and tf_backend_secondary_region parameters |
what was the solve for you with these? |
Check that you are login to AWS using the control manager account user and not the aft account user: $ aws sts get-caller-identity |
I
Simply adding a tf_backend_secondary_region solved this problem for me |
Hi Team,
i have used the learn-terraform-aws-control-tower-aft code and updated with all variables and credentials, but i am landing on the below error. Any solution for this, i didn't see "AWSControlTowerExecution" role in aws console.
PS D:\aws\learn-terraform-aws-control-tower-aft> terraform plan
╷
│ Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::720276729955:role/service-role/AWSControlTowerExecution) cannot be assumed.│
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid
│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors
│
│
│ with module.aft.provider["registry.terraform.io/hashicorp/aws"].aft_management,
│ on .terraform\modules\aft\providers.tf line 12, in provider "aws":
│ 12: provider "aws" {
│
╵
╷
│ Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::720276729955:role/AWSControlTowerExecution) cannot be assumed.
│
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid
│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors
│
│
│ with module.aft.provider["registry.terraform.io/hashicorp/aws"].tf_backend_secondary_region,
│ on .terraform\modules\aft\providers.tf line 26, in provider "aws":
│ 26: provider "aws" {
│
╵
╷
│ Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::926801877456:role/AWSControlTowerExecution) cannot be assumed.
│
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid
│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors
│
│
│ with module.aft.provider["registry.terraform.io/hashicorp/aws"].audit,
│ on .terraform\modules\aft\providers.tf line 40, in provider "aws":
│ 40: provider "aws" {
│
╵
╷
│ Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::081061263646:role/AWSControlTowerExecution) cannot be assumed.
│
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid
│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors
│
│
│ with module.aft.provider["registry.terraform.io/hashicorp/aws"].log_archive,
│ on .terraform\modules\aft\providers.tf line 54, in provider "aws":
│ 54: provider "aws" {
Thanks,
Omkar
The text was updated successfully, but these errors were encountered: