You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Enhancement]: Support alarm tag propagation in CloudWatch alarm action and event payloads #50590
Amazon CloudWatch now supports including alarm tags in SNS notifications, Lambda invocations, and EventBridge alarm state change events.
Please add support for configuring this feature on CloudWatch alarm resources through the ActionConfiguration.AlarmTagsPropagation API field, including:
Enabled: Enable or disable tag propagation.
IncludedTagKeys: Propagate only the specified tag keys.
ExcludedTagKeys: Propagate all tags except the specified tag keys.
IncludedTagKeys and ExcludedTagKeys are mutually exclusive. When propagation is enabled and neither list is specified, CloudWatch includes all eligible alarm tags.
Affected Resource(s) or Data Source(s)
aws_cloudwatch_metric_alarm
aws_cloudwatch_composite_alarm
Potential Terraform Configuration
resource"aws_cloudwatch_metric_alarm""example" {
alarm_name="backend-errors"alarm_description="Backend error count exceeded the threshold."namespace="Application"metric_name="ErrorCount"comparison_operator="GreaterThanOrEqualToThreshold"evaluation_periods=1period=300statistic="Sum"threshold=1treat_missing_data="notBreaching"alarm_actions=[aws_sns_topic.alerts.arn]
tags={
Environment ="production"
Service ="backend"
Team ="platform"
}
action_configuration {
alarm_tags_propagation {
enabled=trueincluded_tag_keys=["Environment", "Service", "Team"]
# Alternatively, use excluded_tag_keys instead.# Omit both lists to propagate all eligible tags.
}
}
}
This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀
Voting for Prioritization
Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
Please see our prioritization guide for additional information on how the maintainers handle prioritization.
Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
Activity
github-actions commentedon Oct 22, 2026
Community Guidelines
This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀
Voting for Prioritization
Volunteering to Work on This Issue