-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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 creating AWS session: CredentialRequiresARNError: credential type source_profile requires role_arn #9999
Comments
Maybe related to hashicorp/aws-sdk-go-base#4? |
+1 I'm also seeing the same error with the provider version > |
Same, getting both above errors using provider |
This PR was merged: hashicorp/aws-sdk-go-base#5 but I believe it needs to be pulled in the providers. |
@ewbankkit we just tested with
provider "aws" {
alias = "prod-us-west-2"
region = "us-west-2"
version = "= 2.33.0"
profile = "prod"
allowed_account_ids = ["123456789"]
}
|
@scalp42 Your AWS CLI config file looks a bit weird to me. |
@ewbankkit I had some left over from debugging >< We can confirm it works on "latest all the things":
Thank you a lot for the help! That S3 backend issue has been holding us off for a while and we kept retrying every week. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Hi folks,
Using Terraform
0.12.5
(as the S3 backend issue is still here for us), we're still running into somewhat the same issue as #9617 except we can initialize the backend fine this time.Using
2.20.0
:Using
2.26.0
:Everything was working fine using
0.11.x
with2.20
and we're 100% sure it's not a credentials/bad setup with AWS creds.TLDR:
0.12.8
= can't initialize due to S3 backend issue0.12.5
and AWS provider2.20
= broken withNo valid credential sources found for AWS Provider
0.12.5
and AWS provider2.26
= broken withNo valid credential sources found for AWS Provider
andCredentialRequiresARNError
supposedly fixed in Can't initialize backend since provider > 2.20 #9617Thanks a lot in advance the migration to 0.12.x has been very painful and is still not successful for us.
The text was updated successfully, but these errors were encountered: