metric alarm resource does not have support for trimmed mean statistic

[blackknight467]

Trying to create a metric alarm with Trimmed Mean (TM) results in the following error

│ Error: invalid value for extended_statistic (must specify a value between p0.0 and p100)

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 v1.0.9
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.68.0
+ provider registry.terraform.io/hashicorp/cloudinit v2.2.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.7.1
+ provider registry.terraform.io/hashicorp/local v2.1.0
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/terraform-aws-modules/http v2.4.1

Affected Resource(s)

• aws_cloudwatch_metric_alarm

Terraform Configuration Files

resource "aws_cloudwatch_metric_alarm" "example" {
  ...
  extended_statistic  = "tm99"
  ...
}

Debug Output

This fails the validation step

Panic Output

Expected Behavior

A metric alarm should be created with trimmed mean

Actual Behavior

Validation fails

Steps to Reproduce

Try to create a trimmed mean metric alarm

1. terraform apply

Important Factoids

N/A

References

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Statistics-definitions.html

[ewbankkit]

The tm99 and other statistics are show in the Console's drop-down:

[xoob]

It looks like this is caused by the client-side validation at

terraform-provider-aws/internal/service/cloudwatch/metric_alarm.go

Line 238 in 01132fc

ValidateFunc: validation.StringMatch(regexp.MustCompile(`p(\d{1,2}(\.\d{0,2})?|100)`), "must specify a value between p0.0 and p100"),

. Would it be feasible to remove the validation and let the AWS API decide what is an acceptable value?

[EpicWink]

Please also support the expandable statistics (docs), including one- and two-value arguments, and both percentage and absolute values

[EpicWink]

Related: #13622

[github-actions]

This functionality has been released in v4.4.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.