Auto Scaling is a management service that allows users to automatically adjust elastic computing resources according to business needs and policies. This way, ECS instances can be added automatically to support traffic peaks, and removed when traffic returns to a normal condition to save costs.
A scaling group is a collection of ECS instances with similar configuration deployed in an application scenario. The minimum and maximum number of ECS instances can be configured for the scaling group. Associated Server Load Balancer instances, RDS instances, and attributes can also be configured.
Scaling configuration defines the ECS instances information used for Auto Scaling.
A scaling rule defines scaling activities, such as adding or removing ECS instances.
When a scaling rule is triggered, a scaling activity takes place. Scaling activities describe the changes of the ECS instances in a scaling group.
These tasks are used to trigger scaling rules, such as a scheduled task or a CloudMonitor alarm task.
Once a scaling activity is completed within a scaling group, cool-down time refers to a period of time when no activities are executed.
- A scaling group contains scaling configuration, scaling rules, and scaling activities.
- Scaling configuration, scaling rules, and scaling activities are associated with the lifecycle management of a scaling group. Deleting the scaling group also deletes the associated scaling configuration, scaling rules, and scaling activities.
- Scaling trigger tasks include scheduled tasks and CloudMonitor alarm tasks.
- Scheduled tasks are independent of the scaling group. Deleting the scaling group will not delete the scheduled tasks.
- CloudMonitor alarm tasks are independent of the scaling group. Deleting the scaling group does not delete the CloudMonitor alarm tasks.