DevOps Notifications with AWS Chatbot - Integrating AWS Events with Slack / Teams
This article introduces how to build a ChatOps environment that delivers CloudWatch alarm and CodePipeline notifications to Slack / Teams and lets you operate AWS from chat with @aws commands.
How Chatbot Works and Supported Services
AWS Chatbot (now named Amazon Q Developer in chat applications) is a ChatOps service that delivers AWS notifications to chat channels such as Slack and Microsoft Teams and lets you operate AWS from there. By associating an SNS topic with a chat channel, messages published to that topic are posted to the chat. The supported AWS services cover a wide range, including CloudWatch alarms, AWS Health, Security Hub, Budgets, CodePipeline, CodeBuild, GuardDuty, Systems Manager, and Config. Notifications are displayed in a format specific to each service, and CloudWatch metrics can be attached as graphs.
Notification Setup and ChatOps
The setup takes three steps. You connect a Slack workspace or a Teams tenant to Chatbot, select a channel, and associate an SNS topic. With CloudWatch alarm notifications, a message is posted to the Slack channel when an alarm transitions to the ALARM state, and a graph of the metric is attached. With the ChatOps feature, you can run the AWS CLI from a chat channel with @aws commands. For example, you can invoke a Lambda function with @aws lambda invoke --function-name my-function, or list the alarms in the alarm state with @aws cloudwatch describe-alarms --state-value ALARM. During incident response, you can carry out both checking the situation and taking action in the chat channel, which lets you reduce the effort of switching screens.
Security and Access Control
You associate an IAM role with a Chatbot channel configuration to control which AWS operations can be run from that channel. One possible configuration is to allow production operations only from a dedicated ops channel and to allow only read-only operations in general development channels. Before running a command, Chatbot checks whether it is permitted by the channel's IAM role and guardrail policies, so narrowing the IAM actions you allow can reduce the risk of a mistaken operation reaching the production environment. Chatbot operation logs are recorded in CloudTrail, so you can audit who ran which command and when. Chatbot itself is free to use, and only SNS delivery charges apply.
Chatbot Pricing
AWS Chatbot is available at no charge. No additional charges apply for delivering notifications to Slack or Teams or for running the AWS CLI from chat. The only costs are the SNS topics that trigger notifications (about $0.50 per 1 million requests) and the charges for resources created / changed as a result of AWS operations run through ChatOps (as of August 2026). Because you can introduce it without additional charges, you can consider it as a way to improve operational visibility and response speed.
Organizing Notifications and Reducing Noise
When there are too many notifications, important alerts get buried. If you split channels by purpose, routing production incidents to a dedicated channel and information sharing to another channel, you can reduce oversights. You prepare SNS topics for each severity level and design which topic flows to which channel in the Chatbot channel configuration. The key is to narrow notifications down to the ones that require action instead of sending every alarm uniformly. By maintaining a state in which someone responds whenever a notification arrives, the chat continues to function as a meaningful operations hub.
Effective Integration with CloudWatch Alarms
To get the value out of Chatbot, the quality of the alarms you send is important. Using composite alarms that combine multiple conditions suppresses false alerts caused by temporary fluctuations in a single metric and makes it easier to notify only for problematic situations. If an alarm includes information that shows what is happening and the steps to check first, the person who receives it can act right away. Because a graph of the alarm state is attached, you can create a flow in which you grasp the trend in the chat and move to the console only when you need to dig deeper.
Choosing Between Chat and Other Notification Methods
Chat notifications are well suited to delivering information to the place the team looks at every day. On the other hand, when you need to wake up the person in charge for a critical incident late at night, it is realistic to combine chat with a dedicated on-call platform that makes phone calls or sends push notifications. A division of roles is effective, in which Chatbot handles daytime collaborative response and situational visibility, and severities that require escalation flow to the on-call route. If you use SNS as a hub, you can deliver the same event simultaneously to multiple routes, such as chat, email, and on-call tools, and reduce missed notifications.
Best Practices for ChatOps Operations
The convenience of operating AWS from chat goes hand in hand with the risk of mistaken operations. You narrow the IAM role granted to each channel to least privilege and separate channels that are mainly for reading from channels that allow limited change operations. It is safe, as a rule, to route destructive operations on production through the official pipelines and runbooks, and to limit chat to checking the situation and minor responses. Because execution logs remain in CloudTrail, you review the operation history regularly. If you pin frequently used investigation procedures to the channel, it becomes easier to avoid response work concentrating on specific people.
Summary
AWS Chatbot is a ChatOps service that turns Slack and Teams into an operations hub for AWS. You can build an operation in which you notice incidents early through alarm notifications, move the response forward with AWS operations from chat, and control access with IAM roles. Another attraction is that it is free to use and has a low barrier to introduction.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
- AWS Chatbot official page
- Amazon SNS official page
- Amazon CloudWatch official page
- AWS Documentation (official)
If this page and the official documentation disagree, treat the official documentation as authoritative.