fbpx

Setting Up Elastigroup’s Notifications

Elastigroup’s Notifications allow you to receive notifications for different events in the Elastigroup based on SNS or other subscriptions like Email or HTTP endpoints. This article covers getting started with Elastigroup’s Notifications and customizing the notifications content to meet your needs.

Prerequisites
  • A running Elastigroup
Step 1: Open the Notifications Modal 

In your Elastigroup click on the Actions button and select Add Notifications.

 

 

 

 

 

 

Click the Subscribe or Subscribe to a Notification button.

 

 

 

 

Note: Existing notifications can’t be modified. To make changes create a new notification and remove the old one.

 

Step 2: Configure Notification

To set up a notification, select the SNS Topic ARN from the Drop down selection and specify the event that you would like to be notified about.

 

 

 

 

 

 

 

Note: Setting up Notifications for additional Platforms like “http”, “https”, “email”, “email-json” are currently only available via our API.

Step 3: Event Types

Group Deployment Completed – You will get notified when deployment process has finished successfully (for more information please see: Deploy).

Group Deployment Failed – You will get notified when deployment process has failed to finish with errors (for more information please see: Deploy).

Group Update Completed – You will get notified when the Elastigroup updated successfully. This can be useful if you would like to monitor Elastigroup updates by other users or provisioning tools.

Instance Launch – You will get notified when a new instance is launched in the Elastigroup.

Instance Terminate – You will get notified when one of your instances has been marked for termination. This notification will be issued prior to `Instance Terminated`.

Instance Terminated – You will get notified when one of the instances was terminated.
Scale Failed – Max Capacity – You will get notified when the group hits the max capacity defined in the Elastigroup, preventing additional scale up actions from taking place.

Unhealthy Instance – You will get notified when one of the instances in your group recognized as unhealthy according to the Health check available by the Load balancer configured in the Elastigroup. This will also apply for HCS users.

Step 4: Format (optional)

In the “Format” field you can optionally change the default output of the notification.

The format of the notification content supports the following variables: instance-id, event, resource-idresource-name,resource-idsubnet-idavailability-zone

 

Default Notification Content:

{
     "event": "<event>",
     "instanceId": "<instance-id>",
     "resourceId": "<resource-id>",
     "resourceName": "<resource-name>"
}

Custom Content Format Example:

{
    "event": "%event%",
    "resourceId": "%resource-id%",
    "resourceName": "%resource-name%",
    "myCustomeKey": "My content is set here",

   "AWS_Account_ID": "1234567890"
}

Instance Launch:

{

"default": "spotinst:notification:instance",

"event": "AWS_EC2_INSTANCE_LAUNCH",

"instanceId": "i-0d1c09565f353e90e",

"resourceId": "sig-675240da",

"resourceName": "ElasticSearch_Test"

}

Instance Terminated:

{
 "default": "spotinst:notification:instance",
 "event": "AWS_EC2_INSTANCE_TERMINATE",
 "instanceId": "i-0d1c09565f353e90e",
 "resourceId": "sig-675240da",
 "resourceName": "ElasticSearch_Test"
}

 

What’s Next