-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
aws provider credentials through vault #14200
Comments
Hi @oillio! Sorry this didn't work out. I think unfortunately this may be the same issue covered in #4149, but I agree that it's weird. If you could share the full output of |
getting the issue!!!
|
Hi @ankitkl! First of all, just to be safe I replaced some key-looking-things in your comment with As mentioned in my previous comment, it would be very helpful to see the full output of your run |
@apparentlymart I have already edit the sensitive before placing here 😀 |
You helpfully shared the config, but to understand what is going on I really need to see the console output from |
Here is my updated code !! While doing plan getting this below error
|
The crash was addressed in #14435 There's a known issue with resource <-> provider block dependency/reference yet to be resolved - #12393 or #4149 respectively which is very likely the cause of the mentioned |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I am trying to use vault to generate credentials for an AWS provider:
This gives the error: AuthFailure: AWS was not able to validate the provided access credentials
It will pull the data values if they are saved in the state. If I provide credentials some other way, and apply this such that the aws_auth fields are set to tfstate, this config will work going forward. However, as vault will expire the provided credentials, it will eventually begin failing again.
This may be related to #4149. I created a new issue as I don't see a chicken and egg problem here. From what I understand, terraform should be able to generate the credentials from vault first and then use them in the aws provider with current functionality.
The text was updated successfully, but these errors were encountered: