1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi,
Yes, this should work.
What I would suggest is to use this same notification to trigger another channel in parallel to Slack in order to isolate the root cause of your problem: Slack or setup of your notification.
Please, follow this documentation to setup the parallel email notification: https://docs.aws.amazon.com/sns/latest/dg/sns-email-notifications.html
Also this very recent post sending alerts on idle EC2 instances may help you in your setup: https://aws.amazon.com/blogs/compute/hibernating-ec2-instances-in-response-to-a-cloudwatch-alarm/
Best
Didier
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
Thanks for your reply. Links you provided are not relevant to specific use case i was working. However, just wanted to update that my configuration worked. May be there was some delay in pulling the notification by AWS Chatbot
Happy that you found a solution! Thanks for confirming