You can change the scaling group's launch configuration, VPC subnet(s), cooldown period, and
health check grace period here.
If a VPC network was selected for the scaling group, the VPC network and its subnets display.
If no VPC network was selected, the VPC components are not shown and the availability zone(s) are editable.
-
To change the launch configuration, select a new one from the Launch
Configuration drop-down list box. A launch configuration
defines the properties of the instances that are launched as part of your
auto scaling group.
-
For VPC networks, the following options are available:
-
You can add VPC subnets by selecting them from the VPC subnet(s) field.
Note: You can remove a selected VPC subnet by clicking on the X next to the IP address associated with each subnet in the
VPC subnet(s) field.
-
If a VPC network was associated with your scaling group, availability zones are view-only and are not editable.
Otherwise, you can add availability zones by selecting them from the Availability Zones field.
Note: You can remove a selected availability zone by clicking on the
x next to the availability zone's name in the
Availability Zones field.
-
The Load balancer(s) field lists all the load balancers associated with the scaling group.
-
You can change the amount of time after a scaling activity completes before any new scaling activity can start
by editing the cooldown period, in seconds, in the Default cooldown period (secs) control.
-
You can change the amount of time after a new instance is launched in your auto scaling group before health checks start
for the instance by editing the grace period, in seconds, in the Health check grace period (secs) control.
Note: The auto scaling health check uses EC2 instance status checks to determine the
health state of each instance in your auto scaling group.