Closed toadjaune closed 11 months ago
Also, I'm wondering if maybe it would be more relevant to implement this directly in gocloud ?
This approach could work too, maybe that's the cleanest one : https://github.com/hashicorp/terraform-provider-aws/issues/28762
I just realized that this feature was already supported, with the following configuration options :
I have no idea how I missed them when first searching through this documentation.
Sorry about that, and thanks again for the great work !
Terraform Version
Should affect all verisons, but there you go :
Affected Resource(s)
This issue affects the provider configuration itself, when connecting to AWS. You may therefore consider it affects all resources.
Terraform Configuration Files
The following configuration is a workaround leveraging the AWS cli to achieve the expected goal.
Here is a more complete example, with more context.
Debug Output
Not relevant
Panic Output
N/A
Expected Behavior
I would have hoped to be able to connect through AWS IAM database authentication natively, without resorting to using the AWS cli.
Actual Behavior
I had to find the workaround mentioned above.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
iam_database_authentication_enabled = true
<your_username>
on it, withLOGIN
,rds_iam
role, and no password.external
provider, fail to do so.Important Factoids
None
References
AWS docs on IAM database authentication