AWS notifications in Slack, explained
You want AWS notifications in Slack, but not the raw notice pasted into a channel: a short summary anyone can read, with a separate channel for each customer. With Sabaki that takes a mail forwarding rule and a Slack incoming webhook, and nothing changes on the AWS side.
Last updated: 2026-09-22
Why leaving it in the mailbox does not work
AWS notifications arrive at the account's contact email address. There they stay, in the mailbox of whoever saw them: the rest of the team never hears about it, and neither does the customer. There are apps that forward the mail to Slack as it is, but then what gets pasted into the channel is a long technical notice, and in the end nobody reads it.
What is needed is something else: one plain sentence, with whether anything has to be done and by when, posted to that customer's channel.
Three steps to get it into Slack
The whole of the Sabaki setup happens without opening the AWS console.
- Add a group for that customer and a forwarding address of its own is issued (@in.sabaki.cloud)
- In Gmail or Microsoft 365, create a rule that forwards mail sent by AWS to that address
- Register the incoming webhook URL of that customer's Slack channel as its destination
What arrives in Slack
The first line of the post carries the severity emoji, the customer's name and the summary. Under it come the AWS account and the service affected, the deadline where there is one, the explanation of what is happening, what it affects and what to do, and at the end a link that opens the original in the inbox. A forward whose AWS signature could not be checked is marked “Unverified”, and if the body carries an account ID that is not registered, the post flags it as an unconfirmed AWS account.
Marketing mail and feature announcements are not sent to Slack by default. Mail with nothing to do with AWS that was forwarded by mistake is not delivered either, and if one of Sabaki's own notification emails comes back forwarded, it is stopped as a loop. What reaches the channel is only what is worth reading.
Example: the mail that arrives, and what Sabaki shows
The subject and body imitate a real notification. Account IDs and dates are fictional.
- From
- Amazon Web Services <no-reply-aws@amazon.com>
- Subject
- Action Required: Your AWS payment could not be processed [AWS Account: 123456789012]
Dear AWS Customer,
We were unable to process the payment for your AWS account 123456789012 for the invoice dated 2026-09-03 (JPY 184,230). Please update your payment method or pay the outstanding balance within 15 days to avoid interruption of your AWS services.
The payment for Company A's invoice dated 3 September (JPY 184,230) could not be processed. Unless the payment method is updated or the outstanding balance is paid by 18 September, the services may be suspended.
The usual causes are an expired credit card or a credit limit that has been reached. Tell whoever keeps the books at Company A and ask them to update the payment method in the AWS billing dashboard. Past the deadline this can go as far as resources being stopped, so deal with it before anything else.
In Slack it opens with a single line — “🔴 [Company A] Critical — The payment for Company A's invoice dated 3 September (JPY 184,230) could not be processed. …” — and below it come the deadline, the explanation and the link to the original.
A different destination for each customer
Each customer can have its own Slack channel, or its own email address, as the destination. A customer who does not use Slack is served by email, and nothing is sent to an address until its owner confirms it. You can also post everything into a single channel for your own team.
Pricing
Automatic delivery to Slack and email starts at Team ($19 per month, tax excluded). Team delivers to one channel; from Business ($49) upwards it can be split per customer, a channel and a destination each. On the Free plan ($0) the summary and the explanation are read in the inbox.
Forward one AWS notification and it comes back explained
The Free plan covers one account and one seat, with no credit card. Nothing changes on the AWS side, and no access keys are registered.
Related questions
Related guides
If this helps, pass it on to someone who needs it.