-
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
Unable to Create Cloudwatch Metric/Alarm in Route53 Healthcheck #13895
Comments
On I had to remove |
@mwpeterson I just saw your code here, I was too following this thread. I get below error if I do not delete these two parameters.
And if I delete the two parameters and execute terraform ( Is there any other resource(s) which is doing the magic for you? |
@grayaii it may be possible, but this may be related to which region the CloudWatch alarm is created in, please see the discussion on the open issue: hashicorp/terraform-provider-aws#712 -- I'm going to lock this issue to consolidate discussion to the open issue. |
Terraform Version
0.9.1
and0.9.3
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Expected Behavior
Alarm should have been created and visible in Route53 Healthcheck
Actual Behavior
INSUFFICIENT DATA
state and was not linked to Route53 HealthcheckSteps to Reproduce
run
terraform apply
after copying the above.tf
fileReferences
The text was updated successfully, but these errors were encountered: