aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
ApplicationAutoScaling CloudWatch alarm tags
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::ApplicationAutoScaling::ScalingPolicy
### Resource name
_No response_
### Description
When creating a `AWS::ApplicationAutoScaling::ScalingPolicy` this creates a CloudWatch alarm in the background based on the `TargetTrackingScalingPolicyConfiguration`.
I would like to be able to pass the `Tags` attribute to the `ScalingPolicy` and have this propagate to all resources created under the hood, where I can not explicitly set the `Tags` attribute.
An alternative would be to add the option to specify tags in the `TargetTrackingScalingPolicyConfiguration` and have that propagate to the CloudWatch Alarm(s) created.
Currently it is not possible (that I can see) to tag the CW alarms created for the `AWS::ApplicationAutoScaling::ScalingPolicy` which means there is no way to find out where this originates from in the cost explorer.
### Other Details
_No response_
Contributor guide
Research direction
Start by reviewing the AWS::ApplicationAutoScaling::ScalingPolicy resource and its TargetTrackingScalingPolicyConfiguration. The issue proposes propagating Tags to the CloudWatch alarms created under the hood, either from ScalingPolicy or its target-tracking configuration. Done means users can identify those alarms in Cost Explorer by applying the requested tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100