<p><strong><span style="font-size:16px">Auto Scaling Group</span></strong></p> <p>The auto scaling group is a collection of ECS instances with the same application scenario. This group of instances provide the same application or service that are created according to the same configuration, with attributes such as the maximum and minimum number of instances, the release strategy, and associated ELB instances etc..</p> <p><strong><span style="font-size:16px">Auto Scaling Activities</span></strong></p> <p>The auto scaling group increases or decreases the instances in the auto scaling group according to its own health check and scaling tasks.</p> <p><strong><span style="font-size:16px">Scaling Tasks</span></strong></p> <p>The auto scaling group behavior specified by time and performance, such as adding two instances to the auto scaling group at a specified time.</p> <p><strong><span style="font-size:16px">Scaling Rules</span></strong></p> <p>The scaling rules specify whether to increase or decrease the instances, the number of instances to configure with scaling tasks.</p> <p><strong>Listener</strong></p> <p>The listener is an important function item in the ELB instance, providing the listening port, protocol, ELB algorithm, health check, and configuration of the server resource pool. The operation of the ELB service mainly depends on the user&#39;s creation and configuration of the listener.</p> <p><strong>Cooling Time</strong></p> <p>Within the cool down time, the scaling group will not execute other scaling activities after a scaling activity ( such as adding or removing ECS instances ) is executed.</p> <p><strong>Timing Task</strong></p> <p>A timing task is a scheduled task that performs a specified scaling rule at a specified time, thereby automatically expanding or shrinking computing resources to meet business needs while controlling costs. You can also specify recurring cycles for timing tasks and respond to changes in traffic with flexible rules.</p> <p>If you can accurately predict the change time of the traffic, you can add timing tasks in advance, prepare enough computing resources before the a business&rsquo;s peak period, or release idle computing resources after the peak period.</p>