Overview

Compare the features of different types of scaling groups

If you set Type to ECS when you create a scaling group, the scaling group contains only ECS instances. If you set Type to ECI when you create a scaling group, the scaling group contains elastic container instances. Different types of scaling groups provide different features. The following table compares the features of scaling groups that contain ECS instances and scaling groups that contain elastic container instances.

Scaling group status

The following table describes the status of a scaling group.

Instance configuration source

A scaling group can contain only one active scaling configuration source. For example, if you activate another scaling configuration in a scaling group for which an active scaling configuration is applied, the current launch template or the scaling configuration exits the Active state. For more information, see Overview.

Scaling rule and scaling activity

After you create a scaling group, you must create scaling rules to scale instances in the scaling group.

• Scaling rule: You can create scaling rules to trigger scaling activities in a scaling group or to configure the maximum and minimum numbers of instances in the scaling group. For more information, see Overview.

  Auto Scaling scales ECS instances in a scaling group based on scaling rules and the maximum, minimum, or expected number of ECS instances specified for the scaling group. For example, if you create a scaling rule that can be used to adjust the number of instances in your scaling group to 50 and the maximum number of ECS instances allowed in your scaling group is 45, your scaling group contains only 45 ECS instances after the scaling rule is executed. For more information about the expected number of instances feature, see Expected number of instances.

  You can execute scaling rules by using the following methods:

  • You can manually execute scaling rules.
  • You can use scheduled tasks to execute scaling rules. For more information, see Create a scheduled task.
  • You can use event-triggered tasks to execute scaling rules. For more information, see Overview.
• Scaling activity: A scaling activity is triggered when a scaling rule is executed or when you manually add or remove ECS instances. For more information, see Overview.

  The following rules apply to scaling activities:

  • An ongoing scaling activity cannot be terminated. For example, if a scaling activity is being executed to create 20 ECS instances but only 5 instances have been created, you cannot terminate the scaling activity.
  • If some ECS instances fail to be added to a scaling group during a scaling activity, Auto Scaling considers that the scaling activity is complete. Auto Scaling rolls back only the ECS instances that fail to be added. For example, if a scaling group contains 20 ECS instances and 19 instances are added as the backend servers of the SLB instance that is associated with the scaling group, only the ECS instance that fails to be added is automatically released.
  • Auto Scaling uses Resource Access Management (RAM) to call ECS API operations to create ECS instances. When ECS instances are rolled back, you must continue to pay for the ECS instances until they are released.
  • Scaling activities are affected by the cooldown time feature. During the cooldown time, Auto Scaling rejects all scaling activities triggered by event-triggered tasks. However, when you manually execute a scaling rule or a scheduled task starts to be executed at the specified point in time, Auto Scaling immediately executes the scaling activity and does not wait for the cooldown time to expire. For more information about the cooldown time feature, see Cooldown time.
  • The cooldown time starts after the last ECS instance or elastic container instance is added to or removed from a scaling group during a scaling activity.