aws_cloudwatch_metric_alarm metric_query validation does not allow percentiles (3.44 regression)

[tdmalone]

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 other comments that do not add relevant new information or questions, 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 CLI and Terraform AWS Provider Version

Terraform v0.12.31
+ provider.aws v3.44.0

Affected Resource(s)

• aws_cloudwatch_metric_alarm

Terraform Configuration Files

Debug Output

Panic Output

Expected Behavior

Plan containing a stat of p99 to continue to validate.

Actual Behavior

Error: expected metric_query.1.metric.0.stat to be one of [SampleCount Average Sum Minimum Maximum], got p99

  on ../../modules/cloudwatch-alarm/main.tf line 38, in resource "aws_cloudwatch_metric_alarm" "metric_math":
  38: resource "aws_cloudwatch_metric_alarm" "metric_math" {

Steps to Reproduce

1. terraform apply

Important Factoids

References

• Caused by aws_cloudwatch_metric_alarm metric_query fields should be validated #19567 / r/cloudwatch_metric_alarm - add validation to metric_query.metric.stat + refactor to use expanded/flatteners #19571
• Potential fix at r/cloudwatch_metric_alarm - add validation to metric_query.metric.stat + refactor to use expanded/flatteners #19571 (comment)

[ewbankkit]

Relevant AWS documentation:

• CloudWatch Statistics
• CloudWatch Percentiles

[github-actions]

This functionality has been released in v3.45.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.