The following table describes the usage recommendations:
| Limit Type | Description |
|---|---|
| For a user in a specific region | - A maximum of 20 startup configurations can be created. - A maximum of 20 scaling groups can be created. - The maximum number of CVM instances that can be created is subject to the user's CVM quota. |
| For a scaling group | - There can be only one startup configuration. - A maximum of 200 CVM instances can be scaled up. - A maximum of 100 scaling policies and 10 scheduled tasks can be created. - A maximum of 5 notifications can be created. - A maximum of 10 lifecycle hooks can be created. |
| Others | - The number of instances in a scaling group cannot exceed the upper limit of IP addresses that the VPC subnet can provide. - AS cannot automatically scale the CPU, memory, and bandwidth of CVM instances. - Auto scaling and startup configuration are region-level concepts. They can be used to start or terminate CVM instances only when instances are in the same region. - Only TDMQ Pulsar is supported as the notification method for lifecycle hooks in a scaling group. |