Use a regular notification rule to receive Auto Scaling activity results by internal message and email. When exceptions occur, you handle them manually based on the notification content.
Regular vs. advanced notification rules
Auto Scaling supports two types of notification rules. Confirm which type fits your needs before proceeding.
| Regular notification rule | Advanced notification rule | |
|---|---|---|
| Notification channels | Internal message, email | CloudMonitor, Message Service (MNS) topic, or MNS queue |
| Exception handling | Manual — you act on each notification | Automatic — CloudMonitor or MNS handles exceptions based on custom policies |
| When to use | You want simple notifications and prefer to handle exceptions yourself | You need automated, event-driven responses to scaling activity |
Prerequisites
Before you begin, ensure that:
-
No advanced notification rule exists for the scaling group. If one does, delete it before proceeding — you cannot create a regular notification rule while an advanced notification rule is active.
Create a regular notification rule
-
Log on to the Auto Scaling console.
-
In the left-side navigation pane, click Scaling Groups.
-
In the top navigation bar, select the region where Auto Scaling is activated.
-
Open the scaling group details page using one of the following methods:
-
Click the ID of the scaling group in the Scaling Group Name/ID column.
-
Click Details in the Actions column.
-
-
Click the Notification Rules tab.
-
Configure the notification method and contact:
-
In the Create Regular Rule dialog box, click Message Settings.
-
On the Common Settings page, select Product Message > Notifications Regarding the Creation and Activation of Product Instances, then configure the notification method and contact.
-
-
Back in the Create Regular Rule dialog box, select the scaling events for which to receive notifications, then click OK.
Scaling event Description Successful Scaling Activity ECS instances or elastic instances are added or removed. Scaling Activity Failed The scaling activity is triggered, but ECS instances or elastic container instances are not added or removed. Scaling Activity Rejected The scaling activity request is received but rejected because the trigger conditions are not met.
What's next
To enable automatic exception handling, create an advanced notification rule. You can specify CloudMonitor, an MNS topic, or an MNS queue as the notified party and define custom exception-handling policies. For details, see Create an advanced notification rule.