{"id":60764,"date":"2024-03-15T14:32:44","date_gmt":"2024-03-15T09:02:44","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=60764"},"modified":"2024-03-19T14:51:45","modified_gmt":"2024-03-19T09:21:45","slug":"send-cloudwatch-alarm-to-slack-via-aws-chatbot","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/send-cloudwatch-alarm-to-slack-via-aws-chatbot\/","title":{"rendered":"Send CloudWatch alarm to Slack via AWS Chatbot"},"content":{"rendered":"

Introduction<\/b><\/h2>\n

One of the critical elements for production uptime is Monitoring and Alerts. Irrespective of the infrastructure types such as EC2 Servers, Serverless, containers, or microservices. There will always be observability needs.<\/span><\/p>\n

There are a lot of tools and software in this Observability market. However, this article focuses on cloud platform tools, such as AWS Cloudwatch<\/strong>.\u00a0<\/span><\/p>\n

Objective<\/b><\/h3>\n

This article will help you to understand and configure AWS Cloudwatch to monitor applications efficiently. In this article, you will also see how\u00a0 to send Cloudwatch alarms to Slack using AWS Chatbot integration<\/span><\/p>\n

Prerequisites<\/b><\/h3>\n
    \n
  • AWS Account<\/span><\/li>\n
  • Slack Channel<\/span><\/li>\n<\/ul>\n

    Steps by Step Procedure<\/b><\/h2>\n

    1. CloudWatch Alarm setup for ECS CPU Metric<\/b><\/h3>\n

    In your AWS console, visit <\/span>CloudWatch,<\/b> then to <\/span>Alarms<\/b> and click on <\/span>All-alarms<\/b> under the Alarms menu.<\/span><\/p>\n

    \"\"<\/p>\n

    After clicking on the <\/span>All-alarms<\/b>, you will see a button on the top right named <\/span>Create Alarm<\/b> to create a new alarm. <\/span>Click on <\/span>Create Alarm<\/b> and click on the <\/span>Select Metric<\/span> button. Check the below image for reference.<\/span><\/p>\n

    \"\"<\/span><\/p>\n

    After you click the Select Metric button, you will be asked to fill in the metric of your choice & metric conditions. Check the screenshot below for reference. <\/span>Specify the Conditions as per the requirement, After specifying the conditions click on next to configure the SNS topic.<\/span><\/p>\n

    \"\"<\/span><\/p>\n

    \"\"<\/p>\n

    In the Configure Actions screen, Choose the SNS Topic to receive a notification when an alarm triggers.\u00a0<\/span>Either you can choose your existing SNS topic or Create a new topic.<\/span><\/p>\n

    \"\"<\/span><\/p>\n

    In my case, it is Cloudwatch-SNS-Topic.<\/span><\/p>\n

    Now the Cloud Watch Alarm is ready, Let\u2019s proceed to the Slack Integration with AWS Chatbot.<\/span><\/p>\n

    2. Creating AWS Chatbot and integration of SNS topic and Slack Channel<\/b><\/h3>\n

    In the AWS console, Search\u00a0 and select AWS Chatbot and click on <\/span>Configure New Client<\/span><\/p>\n

    Once you click, you will see two options: Choose <\/span>Slack<\/span> and <\/span>Configure<\/span><\/p>\n

    \"\"<\/span><\/p>\n

    As you click the configure button, you will be redirected to a Slack authorization screen. <\/span>If you are not already logged into Slack using the same browser, you will be asked to log in.<\/span><\/p>\n

    Once you have authorized it, you will be redirected to AWS, and you can see new <\/span>Configured Clients <\/b>with your Slack Organization name.<\/span><\/p>\n

    \"\"<\/span><\/p>\n

    Click on the <\/span>Configure new channel<\/b><\/p>\n

    You Need to fill in the following items :\u00a0<\/span><\/p>\n

      \n
    • Configuration name<\/b>: Name for the Slack channel configuration<\/span><\/li>\n
    • Channel Type<\/b>: Set channel type to be Public or Private<\/span><\/li>\n
    • Name of the Channel<\/b>: Browse and select the channel where the alert should be sent.<\/span><\/li>\n
    • Channel role<\/b>: Leave this as the default. The AWS will create an IAM role.<\/span><\/li>\n
    • Guardrail policy<\/b>: Specify the minimal IAM Policy so that you can prevent Slack from connecting back to AWS. And even if it will limit the permission.<\/span><\/li>\n
    • Notifications<\/b> \u2192 <\/span>SNS Topic<\/b>: Choose the SNS topic where the chatbot would send alerts.<\/span><\/li>\n<\/ul>\n

      After filling out the above details, click on the Configure button. You will now see the screen like this.<\/span><\/p>\n

      \"\"<\/span><\/p>\n

      3. Add the AWS ChatBot App to the Slack Channel<\/b><\/h3>\n

      Open the Slack channel, Goto Channel details tab, and <\/span>Add the AWS Chatbot app<\/b> using the <\/span>Add Apps option<\/span>.\u00a0<\/span><\/p>\n

      In the Search bar, input <\/span>AWS Chatbot<\/b> and choose the <\/span>AWS Chatbot<\/b> App, and click on <\/span>Add<\/b><\/p>\n

      \"\"<\/b><\/p>\n

      A message will pop up saying, \u201cAWS app was added to the channel<\/strong><\/span>\u201d<\/b> on the channel itself.<\/span><\/p>\n

      Conclusion<\/b><\/h2>\n

      Now, whenever the CloudWatch alarm transitions to an ALARM<\/strong> state,<\/span>\u00a0you will be notified here on the Slack channel.<\/span><\/p>\n

      \"\"<\/span><\/p>\n

      <\/div>","protected":false},"excerpt":{"rendered":"

      Introduction One of the critical elements for production uptime is Monitoring and Alerts. Irrespective of the infrastructure types such as EC2 Servers, Serverless, containers, or microservices. There will always be observability needs. There are a lot of tools and software in this Observability market. However, this article focuses on cloud platform tools, such as AWS […]<\/p>\n","protected":false},"author":1741,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":100},"categories":[2348],"tags":[1892],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60764"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1741"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=60764"}],"version-history":[{"count":3,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60764\/revisions"}],"predecessor-version":[{"id":60869,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/60764\/revisions\/60869"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=60764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=60764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=60764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}