cloudwatch alarm with cross-account metric

[nahratzah]

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

Description

Cloudwatch alerts in AWS can consume metrics from a different account.

In order for this to be supported, the AccountId attribute in MetricDataQuery must be exposed.

New or Affected Resource(s)

• aws_cloudwatch_metric_alarm

Potential Terraform Configuration

resource "aws_cloudwatch_metric_alarm" "my_first_alarm" {
    alarm_name        = "my_first_alarm"
    threshold         = 1
    alarm_description = "example alarm"
    
    metric_query {
        id          = "m1"
        account_id  = "123456789" // <-- new attribute
        return_data = true
        
        metric {
            metric_name = "HealthyHostCount"
            namespace   = "AWS/NetworkELB"
            dimentions  = {
                LoadBalancer = "some nlb"
                TargetGroup  = "some tg"
            }
            period  = 60
            stat    = "average"
        }
    }
}

References

• https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html
• https://docs.aws.amazon.com/sdk-for-go/api/service/cloudwatch/#MetricDataQuery

[github-actions]

This functionality has been released in v3.54.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.