tencent cloud

Auto Scaling

Product Introduction
Overview
Strengths
Scenarios
Service Limits
Access Management
Purchase Guide
Getting Started
Creating a Scaling Plan in 5 Minutes
Step 1:Creating a Launch Configuration
Step 2:Creating a Scaling Group
Step 3:Creating a Scaling Policy
Tutorial
Creating Web Services
Creating High-performance Computing Cluster
Creating Servers for Sending Requests
Configuring For High Availability Services
Launch Configuration
Launch Configuration Overview
Creating a Launch Configuration
Viewing Launch Configuration List
Modifying Launch Configurations
Exception Detection
Scaling Groups
Scaling Group Overview
Creating a Scaling Group
Viewing Scaling Group List
Modifying Scaling Groups
Modifying Bound Instances
Adding CLBs
Delete scaling group
Creating Notifications
Creating Scaling Activity Notifications
Specifying Notification Recipients
Expanding and Reducing Capacity
Auto Scaling Lifecycle Hook
Managing Scheduled Actions
Managing an Alarm-triggered Policy
Instance Health Check
Expanding Capacity Manually
Scale-in Process
Viewing Scaling Activities
Suspending and Resuming Scaling
Scale-in Removal Protection
Scaling Activity Cancelled
Scaling Activity Failed
Cooldown Period
Monitoring
Monitor Alarm Metrics
Running Status Check
Scheduled Task
Scheduled Task Execution Time Description
Troubleshooting
Scaling Group Doesn't Work
Scaling Activity Failed
Use Cases
Setting a Fixed Outbound IP Address for Scaling Groups
Deploying Elastic Web Application Service
Enabling Services Upon CVM Start-up
Customer Cases
iCarbonX
API Documentation
History
Introduction
API Category
Making API Requests
Scaling Group APIs
Scaling Group Instances APIs
Launch Configuration APIs
Scheduled Action APIs
Alarm Trigger Policy APIs
Notification APIs
Lifecycle Hook APIs
Instance Refresh APIs
Other APIs
Data Types
Error Codes
FAQs
Contact Us
Glossary
DocumentaçãoAuto ScalingAPI DocumentationAlarm Trigger Policy APIsExecuteScalingPolicy

ExecuteScalingPolicy

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-10-30 21:28:29

1. API Description

Domain name for API request: as.intl.tencentcloudapi.com.

This API is used to execute a scaling policy.

  • The scaling policy can be executed based on the scaling policy ID.
  • The policy cannot be executed if there are ongoing scaling actions on the scaling group.
  • Executing a target tracking policy is not supported.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: ExecuteScalingPolicy.
Version Yes String Common Params. The value used for this API: 2018-04-19.
Region Yes String Common Params. For more information, please see the list of regions supported by the product.
AutoScalingPolicyId Yes String Alarm scaling policy ID. target tracking policy is unsupported. the alert policy type can be obtained via the ScalingPolicyType parameter in the api response of DescribeScalingPolicies.
HonorCooldown No Boolean Whether to check if the auto scaling group is in the cooldown period. Default value: false
TriggerSource No String Source that triggers the scaling policy. Valid values: API and CLOUD_MONITOR. Default value: API. The value CLOUD_MONITOR is specific to the Cloud Monitor service.

3. Output Parameters

Parameter Name Type Description
ActivityId String Scaling activity ID
RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

4. Example

Example1 Triggering a scaling policy

This example shows you how to trigger an alarm scaling policy.

Input Example

POST / HTTP/1.1
Host: as.intl.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: ExecuteScalingPolicy
<Common request parameters>

{
    "HonorCooldown": "false",
    "AutoScalingPolicyId": "asp-f59pppuh"
}

Output Example

{
    "Response": {
        "ActivityId": "asa-o4v87ae9",
        "RequestId": "116213d6-2269-44cc-af76-c4a8dc7dbdf9"
    }
}

5. Developer Resources

SDK

TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

Command Line Interface

6. Error Code

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

Error Code Description
FailedOperation.NoActivityToGenerate No scaling activity is generated.
InternalError An internal error occurred.
InvalidParameter.ActionNotFound Invalid Action request.
InvalidParameterValue.InvalidAutoScalingPolicyId Invalid alarm-triggered policy ID.
InvalidParameterValue.TargetTrackingScalingPolicy Executing a target tracking policy is not supported.
ResourceInUse.AutoScalingGroupNotActive The scaling group is disabled.
ResourceNotFound.AutoScalingGroupNotFound The scaling group does not exist.
ResourceNotFound.ScalingPolicyNotFound The alarm policy does not exist.
ResourceUnavailable.AutoScalingGroupAbnormalStatus The auto scaling group is exceptional.
ResourceUnavailable.AutoScalingGroupInActivity The auto scaling group is active.
Anterior: ModifyScalingPolicyPróximo: DescribeScalingPolicies

Ajuda e Suporte

Esta página foi útil?

comentários