Auto Scaling (AS) is a resource auto-scheduling tool provided by Tencent Cloud. It can dynamically adjust computing resources based on business needs and policies. By setting alarm policies and scheduled tasks, AS can automatically increase or decrease the number of CVM instances and complete the configuration. This ensures service stability during peak business periods and saves resource costs during off-peak periods.
This section introduces the latest AS API interfaces that conform to the OpenAPI 3.0 specification. Subsequent additions will be updated in this section, with priority recommendation to use this version.
You can call APIs to operate AS, such as creating a scaling group, creating a launch configuration, and setting alarm policies. For all supported API information of AS, please refer to the API overview.
For common terms of the AS API interface, see the table below:
| Term | Description |
|---|---|
| A scaling group is a basic unit of auto scaling, consisting of an instance set that follows the same rules and targets the same scenario. | |
| Alarm policy: Rule configuration that triggers scaling actions, supporting dynamic policies based on monitoring metrics. | |
| Instance | A CVM instance is the core compute resource unit managed by AS. |
Usage limits
For AS feature limitations and quota description, please refer to Auto Scaling Usage Limits.
For specific API parameter limits, refer to the parameter descriptions in each API document.
You can use the API Explorer tool to call APIs online.
This document uses creating a scheduled scale-out task as an example. The steps to call the API through API Explorer are as follows:
CreateAutoScalingGroup API (https://www.tencentcloud.com/document/product/377/20440?from_cn_redirect=1) to configure basic scaling rules.CreateScheduledAction API to create a scheduled task for daily expansion during peak business hours.Note:
- All AS APIs in this section are the latest version, API 3.0, and all new features related to AS will be updated in this section. We strongly recommend you to use the latest API 3.0.
피드백