You pay only for the underlying services. There is no additional charge for AWS Chatbot.

I might argue that you have less code to maintain, easier infrastructure, but that wouldn't be a great selling point - we are talking about one single Lambda, which we haven't touched in years - so let me say just this: Once you have your Client, your CDK stack will be able to create a SlackChannel Configuration.īut you are just exchanging Lambda with Chatbot, where's the gain? Reading again the docs here I realised that I was missing the main Workspace/Client Configuration.įrom your account console open AWS Chatbot and select create Client Configuration, grant the permissions for your AWS Chatbot to access your Slack workspace and voila'. In our new SlackNotification stack we still create a Topic, but then instead of creating a Lambda, you set up the configuration of your SlackBot. Of course, Chatbot does a lot more than receiving Slack Notifications - actually it is more a powerful tool to send messages from Slack in order to run some commands on your AWS resources (like launching deployments, starting instances, triggering lambdas and so on) but I will explain that in another post.īut for now let's focus on how Chatbot simplified our Monitoring system basically allowing us to get rid of the Lambda function.

By using AWS Chatbot, you can receive alerts and run commands to return diagnostic information, invoke AWS Lambda functions, and create AWS Support cases so that your team can collaborate and respond to events faster. Recently I was setting up Slack Notifications for a new project on a new team and while I was checking out that old repo and some newer documentation I realised AWS ChatBot exists.ĪWS Chatbot is an interactive agent that makes it easier to monitor and interact with your AWS resources in your Slack channels and chat channels. It was as you can see already simple enough, and we used that for years already. Enter fullscreen mode Exit fullscreen mode

Aws slack chatbot