Terraform fails to create aws_cloudwatch_metric_alarm

[dcgomesbr]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.11.14

• provider.archive v1.2.2
• provider.aws v2.39.0
• provider.null v2.1.2
• provider.random v2.2.1
• provider.template v2.1.2

Affected Resource(s)

• aws_cloudwatch_metric_alarm

Terraform Configuration Files

resource "aws_cloudwatch_metric_alarm" "errors_alert" {

  actions_enabled     = "true"
  alarm_description   = "Anomaly band (12 / 15 min)"
  alarm_name          = "some_alarm_name"
  comparison_operator = "GreaterThanUpperThreshold"
  datapoints_to_alarm = "1"
  evaluation_periods  = "1"
  treat_missing_data  = "breaching"
  threshold           = "0"
  tags                = "${map("Name","same_name")}"

  metric_query {
    id = "m1"

    metric {
      metric_name = "SomeMetric"
      namespace   = "SomeNamespace"
      period      = "900"
      stat        = "Maximum"

      dimensions = {
        Service = "SomeService"
      }
    }
  }

  metric_query {
    id          = "ad1"
    expression  = "ANOMALY_DETECTION_BAND(m1, 12)"
    label       = "SomeLabel"
    return_data = "true"
  }
}

Debug Output

https://gist.github.com/dcgomesbr/5a47c13c8986bcd712a68ad87daae2d1

Panic Output

None

Expected Behavior

Create the Anomaly Band alarm.

Actual Behavior

aws_cloudwatch_metric_alarm.errors_alert: Creating metric alarm failed: ValidationError: ComparisonOperators for ranges require ThresholdMetricId to be set
status code: 400, request id: 01862480-0be5-4132-a5a3-63ee2e0eb4d1

Steps to Reproduce

Plan and apply the resource above.

Important Factoids

I could create the resource manually and import the state in some cases. In other cases, it insists in re-create the metric.query because of return_data != false and fails the same way.

References

None

[justinretzolk]

Hey @dcgomesbr 👋 Thank you for taking the time to file this issue! Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?