-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
InvalidParameterCombination: A MonitoringRoleARN value is required if you specify a MonitoringInterval #136
Comments
👍 - also experiencing the same or similar error |
I created the PRs and tested for terraform 0.11 but could not test for 0.12 since my infra is still 0.11. It would be nice if someone could approve my PRs and also test the 0.12 implementation. EDIT: While the PR is not merged you could use my fork that I used in the PR to solve this issue. |
Just a note, I am also experiencing the same issue and it's still ongoing. |
Me three... on terraform12 |
So... I've heard that this was fixed if you update the aws provider in terraform to 2.25 according to hashicorp/terraform-provider-aws#5559 Can someone do that and let us know? (I currently do not have an RDS to test) |
Just tried and is still not fixed. version = "2.31"
|
I am running into this bug too on aws provider version 2.31. What is weird is that I didnt hit this error when I was bringing up databases a few months ago. Its only happening now when I am bringing up another database. What changed? EDIT: Tried various aws provider versions: 2.20, 2.24, 2.25, 2.31; all same error |
I am getting this error when trying to create a new database as well as when modifying an existing one. |
Well my PR is still open... there's still chance to approve it. It's only a fail safe anyways... |
Big thanks to @flmmartins ! v2.12.0 has been released for Terraform 0.12 users. v1.35.0 has been released for Terraform 0.11 users. |
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. |
Hello All,
I'm trying to set enhanced monitoring for my 2 databases. My plan out is:
I created ONE role for both databases and applied before like below:
Then I call a module which will call terraform-aws-rds:
Inside the actual call I do it:
Execution logs are:
Researching this I found this: hashicorp/terraform-provider-aws#315 (comment)
I cannot confirm but aparently this happens only when you try to modify already created db
Aparently other rds module solved (terraform-aws-postgres...) this... is it possible to do the same here meanwhile? Currently I'm using 1.28.0. Tks
The text was updated successfully, but these errors were encountered: