-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-cloudwatch-actions): Add the possibility to have SSM OpsItem Action #16861
Comments
Thanks for opening this feature request, @vportascarta! I think this would be a great feature to have. To implement, we need to add another action in the In the meantime, you can add the action arn to an Alarm using an escape hatch. Your code could look something like this, where
|
Hi @madeline-k, the PR is already done #16923. |
Thanks for the PR, @vportascarta! Sorry I completely missed that when I was looking at this issue yesterday. |
…#16923) This small PR will add SSM OpsItem action to cloudwatch alarm. The arn format was taken from the alarm UI (in view source) and with all the parameters (severity and category) closes #16861 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…aws#16923) This small PR will add SSM OpsItem action to cloudwatch alarm. The arn format was taken from the alarm UI (in view source) and with all the parameters (severity and category) closes aws#16861 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Description
In addition to these actions : ApplicationScalingAction, AutoScalingAction, Ec2Action, Ec2InstanceAction, SnsAction, add an SystemManagerAction to be able to create OpsItem in SSM in a CW alarm.
Use Case
We need this to group and prioritize all our alarm triggers into OpsCenter instead of using SNS notification.
Proposed Solution
Add an action that build and add the arn into the alarm
"arn:aws:ssm:<region>:<account_id>:opsitem:<severity>#CATEGORY=<category>"
Maybe use enum for severity and category
Other information
On AWS Console UI
Acknowledge
The text was updated successfully, but these errors were encountered: