Overview
An AS group is a basic AS resource. It allows you to group and manage ECSs configured for the same workload. ECSs managed by an AS group are called scaling instances. You can create an AS policy to automatically add or remove instances to or from an AS group, or to maintain a fixed number of instances in the group.
AS Group Capabilities
| Capability | Description |
|---|---|
| Automatically adding instances | ECS instances with specified specifications can be automatically created and added to an AS group. Only pay-per-use or spot ECS instances can be created and added automatically. |
| Automatically removing instances | Instances can be automatically removed from an AS group. |
| Adding a load balancer | A load balancer can be added for an AS group. When an instance is added to an AS group, the instance is automatically added to the backend pool of the load balancer. When an instance is removed from an AS group, the instance is automatically removed from the backend pool of the load balancer. For details, see Creating an AS Group. |
| Instance health check | AS periodically checks the health of instances in an AS group and removes abnormal instances. For details, see Creating an AS Group. |
| Notifications | When a specific event occurs in an AS group, an SMS message or email can be sent to notify you of the event. For details, see SMN Notifications. |
| Lifecycle hooks | You can configure a lifecycle hook for an AS group to pause instance addition or removal. For details, see Lifecycle Hooks. |
| Adding tags | If a tag is added for an AS group, the same tag will also be added for all the instances in the group. For details, see Managing AS Group Tags. |
AS Policy Types
| Type | Triggering Condition | Description |
|---|---|---|
| Alarm-based | Triggered by Cloud Eye alarms. When an alarm of any severity is generated based on a rule, all alarm policies bound to the alarm rule will be executed. | An alarm policy cannot be used until it is bound to an alarm rule. You are advised to bind an alarm rule to a single monitored object and alarm condition. The following alarm rules are not recommended:
|
| Scheduled | Triggered at a specific time point, for example, 12:00 on yyyy-mm-dd. | The schedule is precise down to the minute. |
| Periodic | Triggered at a specified cycle and time point. For example: 12:00 every day 13:00 every Monday and Tuesday 14:00 on the first, second, and third day of each month | The schedule is precise down to the minute. |
Scaling Actions
When instances need to be added to or removed from an AS group, or the load balancer of an AS group needs to be changed, the group will perform various scaling actions.
For details, see Scaling Actions.
Instance Capabilities
| Capability | Description |
|---|---|
| Manually adding instances | You can manually add instances to an AS group. There are no billing-mode restrictions on manually added instances. |
| Manually removing instances | You can manually remove instances from an AS group. |
| Instance protection | You can enable or disable protection for instances in an AS group. |
| Standby instances | You can put instances into or out of standby. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
