A company wants to implement a machine learning-based monitoring solution to identify unexpected cost spikes at the individual AWS service level. Once an anomaly is detected, the SysOps team needs to receive immediate notifications in their Microsoft Teams channel. Which of the following steps are required to implement this solution? (Select TWO.)
- Create an AWS services cost monitor in AWS Cost Anomaly Detection.Answer
- Create an alert subscription linked to the monitor, select an Amazon SNS topic as the alert destination, and configure AWS Chatbot to integrate the SNS topic with Microsoft Teams.Answer
- CCreate an AWS Budget with a daily cost limit and link it directly to an AWS Chatbot client configured for Microsoft Teams.
- DCreate an AWS Cost Anomaly Detection alert subscription and configure it to send notifications directly to a Microsoft Teams webhook URL.
- EConfigure an Amazon EventBridge rule that detects AWS Config resource compliance changes and invokes an AWS Systems Manager Automation runbook to post alerts to Microsoft Teams.
Answer
To monitor individual service costs and alert via Microsoft Teams, you must create an AWS services cost monitor in AWS Cost Anomaly Detection, and create an alert subscription that routes notifications to an Amazon SNS topic, which AWS Chatbot then delivers to the Microsoft Teams channel.
To monitor anomalous spend at the service level, you must create an 'AWS services' monitor in AWS Cost Anomaly Detection. Because Cost Anomaly Detection alert subscriptions only support Amazon SNS and email as destinations, sending alerts to Microsoft Teams requires routing through an Amazon SNS topic. AWS Chatbot can then be configured to subscribe to this SNS topic and deliver the alerts directly to the designated Microsoft Teams channel.
Step-by-Step Solution
Key Concept
Integrating AWS Cost Anomaly Detection with AWS Chatbot and Amazon SNS for automated chat-based alerting on service-level cost anomalies.