AWS-to-Slack
Forward AWS CloudWatch Alarms and other notifications from Amazon SNS to Slack.
What is it?
AWS-to-Slack is a Lambda function written in Node.js that forwards alarms and notifications to a dedicated Slack channel. It self-hosted in your own AWS environment and doesn't have any 3rd party dependencies other than the Google Charts API for rendering CloudWatch metrics.
Supported notification formats:
- AWS Code Build
- AWS CodeCommit
- AWS CodeDeploy 🆕
- AWS Health Dashboard
- Amazon Inspector
- Amazon SES Received Notifications
- CloudWatch Alarms (incl. Metrics)
- Elastic Beanstalk
- RDS
- Generic SNS messages
- Plain text messages
Additional formats will be added; Pull Requests are welcome!
Try!
Ready to try it for yourself? Installation into your own AWS environment is as
simple as pressing the button below (for installation outside of us-east-1
see details below):
Installation
Step 1 - Setup Slack
The Lambda function communicates with Slack through a Slack webhook webhook. Note that you can either create an app, or a custom integration > Incoming webhook (easier, will only let you add a webhook)
- Navigate to https://your-slack-domain.slack.com/apps/manage and click "Add Configuration".
- Choose the default channel where messages will be sent and click "Add Incoming WebHooks Integration".
- Copy the webhook URL from the setup instructions and use it in the next section.
- Click "Save Settings" at the bottom of the Slack integration page.
Step 2 - Configure & Launch the CloudFormation Stack
Note that the AWS region will be the region from which you launch the CloudFormation wizard, which will also scope the resources (SNS, etc.) to that region.
Launch the CloudFormation Stack by using our preconfigured CloudFormation template or by simply pressing the following button:
Region | Launch Stack |
---|---|
us-east-1 | |
us-east-2 | |
us-west-1 | |
us-west-2 | |
ap-northeast-1 | |
ap-northeast-2 | |
ap-south-1 | |
ap-southeast-1 | |
ap-southeast-2 | |
ca-central-1 | |
eu-central-1 | |
eu-west-1 | |
eu-west-2 | |
eu-west-3 | |
sa-east-1 |
Afterwards
Click "Next" and on the following page name your new stack and paste the webhook URL from before into the "HookUrl" field. You can also configure a different channel to post to if wanted.
Click "Next" again, complete the stack setup on the following pages and finally launch your stack.
Step 3 - Subscribe to Triggers
Before the Lambda function will actually do anything you need to subscribe it to actual CloudWatch alarms and other SNS triggers. Open up the AWS Lambda, switch to the "Triggers" tab and subscribe for all events you're interested in.
Setting Up AWS CodeBuild
CodeBuild integration was suggested by ericcj and is based on the Medium post Monitor your AWS CodeBuilds via Lambda and Slack by Randy Findley.
To enable CodeBuild notifications add a new CloudWatch Event Rule, choose CodeBuild
as source and CodeBuild Build State Change as type. As Target select the aws-to-slack
Lambda. You can leave all other settings as is. Once your rule is created all CodeBuild
build state events will be forwarded to your Slack channel.
Setting Up AWS CodeCommit
Similar to the CodeBuild integration, CodeCommit notifications are triggered by CloudWatch Event Rules. Create a new CloudWatch Event Rule, select CodeCommit as the source, and select one of the supported event types:
- CodeCommit Pull Request State Change - Will generate events when a pull request is opened, closed, merged, or updated.
- CodeCommit Repository State Change - Will generate events when a branch or tag reference is created, updated, or deleted.
Add the aws-to-slack
lambda as the target. No other settings are needed.
Contributing
You want to contribute? That's awesome! 🎉
Check out our issues page for some ideas how to contribute and a list of open tasks. There're plenty of notification formats that still need to be supported.
The repository comes with a very simple Makefile
to build the CloudFormation
stack yourself. Simply run
make deps
make package
To generate a new release.zip
in the build
folder. Upload this zip to your
AWS Lambda function and you're good to go.