- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
APIs
- AS Groups
- AS Configurations
- Instances
-
AS Policies
- Creating an AS Policy
- Creating an AS Policy (V2)
- Modifying an AS Policy
- Modifying an AS Policy (V2)
- Querying AS Policies Bound to an AS Group
- Querying AS Policies Bound to a Scaling Resource (V2)
- Querying AS Policies (V2)
- Querying an AS Policy
- Querying an AS Policy (V2)
- Executing, Enabling, or Disabling an AS Policy
- Deleting an AS Policy
- Batch Managing AS Policies
- AS Policy Execution Logs
- Scaling Action Logs
- Quotas
- Notifications
- Lifecycle Hooks
- Tags
- API Version Query
- Application Examples
- Permissions Policies and Supported Actions
- Appendix
- Change History
- SDK Reference
-
FAQs
-
General
- What Are Restrictions on Using AS?
- Must I Use AS Together With ELB and Cloud Eye?
- Is AS Billed?
- Will an Abrupt Change in Monitoring Metric Values Trigger an Unnecessary Scaling Action?
- How Many AS Policies and AS Configurations Can I Create and Use?
- Can AS Automatically Scale Up or Down vCPUs, Memory, and Bandwidth of ECSs?
- What Is an AS Quota?
- How Do I Fix the Error "The key pair does not exist" When I Connect to an Instance?
- What Types of EIP and Shared Bandwidths Can Be Adjusted by AS?
- What Types of ECS and HECS Instances Can Be Scaled by AS?
- If the OS of an ECS Instance in an AS Group Is Upgraded, Can AS Automatically Add Instances with the Newest OS During the Next Scale-out Action?
- Can AS Add Yearly/Monthly ECS Instances When It Scales Out an AS Group?
- Can AS Increase Bandwidths as Required?
- AS Group
-
AS Policy
- How Many AS Policies Can I Enable?
- What Are the Conditions to Trigger an Alarm-based AS Policy?
- What Is a Cooldown Period and Why Is It Required?
- Can AS Scale Capacity Based on Custom Monitoring by Cloud Eye?
- What Monitoring Metrics for an AS Group Will Be Affected If VM Tools Are Not Installed on the Instances in the Group?
- What Can I Do If an AS Policy Fails to Be Enabled?
- How Do I Install the Agent on Instances in an AS Group to Use Agent Monitoring Metrics?
-
Instance
- How Do I Prevent Instances Manually Added to an AS Group from Being Automatically Removed?
- When an Instance Is Removed from an AS Group and Deleted, Is the Application Data Saved?
- Can I Add Yearly/Monthly ECS Instances to an AS Group?
- Can AS Automatically Delete Instances Added Based on an AS Policy When They Are Not Required?
- What Is the Expected Number of Instances?
- How Do I Delete an ECS Instance Created in a Scaling Action?
- Will ECS Instances Be Deleted If They Become Unhealthy?
- How Do I Handle Unhealthy Instances in an AS Group?
- Why Instances in an AS Group Keep Failing Health Checks and Getting Deleted and Recreated?
- How Do I Prevent Instances from Being Automatically Removed from an AS Group?
- Why Is an Instance that Was Removed from an AS Group and Deleted Still Displayed in the ECS List?
- Do I Need to Bind an EIP to an Instance Before I Manually Add the Instance to an AS Group?
- Can I Apply the Configurations of an Existing Instance in an AS Group to Instances to Be Added in the Future?
- Will the System Bind a New EIP or an Existing One a Newly Added ECS Instance?
-
Others
- How Can I Automatically Deploy My Application on an Instance?
- How Does Cloud-Init Affect the AS Service?
- Why Can't I Use a Key File to Log In to an ECS?
- Do I Need to Configure an EIP in an AS Configuration When a Load Balancer Has Been Enabled for an AS Group?
- How Do I Enable Automatic Initialization of EVS Disks on Instances that Have Been Added to an AS Group During Scaling Actions?
-
General
- Videos
Managing AS Policies
Scenarios
An AS policy specifies the conditions for triggering a scaling action as well as the operation that will be performed. If the conditions are met, a scaling action is triggered automatically.
This section describes how to manage an AS policy, including modifying, enabling, disabling, executing, and deleting an AS policy.
Modifying an AS Policy
If a particular AS policy cannot meet service requirements, you can modify the parameter settings of the policy.
- Log in to the management console.
- Under Compute, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
- Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and choose More > Modify in the Operation column.
- In the displayed Modify AS Policy dialog box, modify the parameters and click OK.
Enabling an AS Policy
An AS policy can trigger scaling actions only when it and the AS group are both enabled. You can enable one or more AS policies for an AS group as required.
- Before enabling multiple AS policies, ensure that the AS policies do not conflict with one another.
- An AS policy can be enabled only when its status is Disabled.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Enable in the Operation column. To concurrently enable multiple AS policies, select these AS policies and click Enable in the upper part of the AS policy list.
Disabling an AS Policy
If you do not want a particular AS policy to trigger any scaling actions within a specified period of time, you can disable it.
- If all of the AS policies configured for an AS group are disabled, no scaling action will be triggered for this AS group. However, if you manually change the value of Expected Instances, a scaling action will still be triggered.
- You can disable an AS policy only when its status is Enabled.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Disable in the Operation column. To concurrently disable multiple AS policies, select these AS policies and click Disable in the upper part of the AS policy list.
Manually Executing an AS Policy
You can make the number of instances in an AS group reach the expected number of instances immediately by manually executing an AS policy.
- You can manually execute an AS policy if the scaling conditions configured in the AS policy are not met.
- You can manually execute an AS policy only when the AS group and AS policy are both in Enabled state.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and click Execute Now in the Operation column.
- If Policy Type is set to Alarm and Alarm Policy Type to Refined scaling, the scaling policy cannot be executed immediately.
Deleting an AS Policy
You can delete an AS policy that will not be used for triggering scaling actions.
An AS policy can be deleted even when the scaling action triggered by the policy is in progress. Deleting the AS policy does not affect a scaling action that has already started.
Locate the row containing the target AS group and click View AS Policy in the Operation column. On the displayed page, locate the row containing the target AS policy and choose More > Delete in the Operation column.
To concurrently delete multiple AS policies, select these AS policies and click Delete in the upper part of the AS policy list.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.