(aws-cloudwatch-actions): Add the possibility to have SSM OpsItem Action

[vportascarta]

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

• I may be able to implement this feature request
• This feature might incur a breaking change

[madeline-k]

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 aws-cloudwatch-actions module here: https://github.com/aws/aws-cdk/tree/master/packages/%40aws-cdk/aws-cloudwatch-actions/lib.
If you are willing to open a PR that would be great! Take a look at our contributing guide to get started.

In the meantime, you can add the action arn to an Alarm using an escape hatch. Your code could look something like this, where scope is the relevant scope, it probably would be this:

  const cfnAlarm = Node.of(alarm).defaultChild as cloudwatch.CfnAlarm;
  cfnAlarm.alarmActions?.push(`arn:aws:ssm:${Stack.of(scope).region}:${Stack.of(scope).account}:opsitem:<severity>#CATEGORY=<category>`);

[vportascarta]

Hi @madeline-k, the PR is already done #16923.
Please let me know if it needs something else to implement this feature.

[madeline-k]

Thanks for the PR, @vportascarta! Sorry I completely missed that when I was looking at this issue yesterday.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.