CloudWatch Evidently: Use Case for Associated Alarms
A CloudWatch Evidently Launch can be associated with an alarm, but I can't seem to find any follow-up actions that I can trigger based on that alarm, e.g. stopping the launch or modifying the traffic.
Did I miss something or what's the actual use-case here?
- 新しい順
- 投票が多い順
- コメントが多い順
Hi Tobias,
Associating a CloudWatch alarm with Evidently is optional [1]. If you create at least one metric for the launch, you can associate an existing CloudWatch alarm with this launch. To do so, choose Associate CloudWatch alarms.
About the CloudWatch alarm actions, these actions [2] are same as you configure during alarm creation. The use case will be to take any actions from below:
- notification to SNS topic
- Lambda action
- Auto scaling action
- EC2 action
- Ticket action
If your use case is to start/stop the launch then you can create a lambda function using CloudWatch Evidently stop_launch or start_launch boto3 [3] and call that in the alarm Lambda action.
[1]. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Evidently-newlaunch.html [2]. https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html [3]. https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/evidently.html
Hope this helps
関連するコンテンツ
- 質問済み 10ヶ月前
AWS公式更新しました 8ヶ月前
Thank you!
So there's no Evidently-"built-in" action that can be configured in the Evidently UI? What's the benefit of connecting the launch with the alarm if the alarm actions have to be configured independently of the feature launch?