-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
New Resource: Amazon CloudWatch Anomaly Detector #10551
Comments
I believe that this is a duplicated issue. First request to implement cw anomaly is below: |
EDIT: Actually this is not a duplicate -- there is a separate API for anomaly detectors as mentioned in the issue description: https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutAnomalyDetector.html Sorry for the errant close. |
Please correct me if im wrong but both requests are for cloud watch anomaly detection in cloud watch alarms :) |
Correct me if I am wrong, but will there not be a aws_cloudwatch_anomaly_detector resource then? Just use aws_cloudwatch_metric_alarm instead right? |
@cougar2009 that's correct https://www.terraform.io/docs/providers/aws/r/cloudwatch_metric_alarm.html#example-with-an-expression (2nd example) |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
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. |
Community Note
Description
Amazon CloudWatch Anomaly Detection is now available in all commercial AWS regions.
New or Affected Resource(s)
aws_cloudwatch_anomaly_detector
Potential Terraform Configuration
References
Announcement.
Blog post.
API reference.
The text was updated successfully, but these errors were encountered: