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

Glossary

Strengths

PDF

フォーカスモード

フォントサイズ

最終更新日: 2024-01-08 17:53:29

Benefits
With Auto Scaling          
Without Auto Scaling
Automatic
Automatically scale instances without manual 
interventionAuto Scaling (AS) automatically and dynamically adds or removes CVM instances in real time based on the business load, ensuring that you are running the optimal number of instances without manual intervention.
For example, you can set a scaling policy to add CVM instances to the scaling group when the CPU utilization is high, and the new CVM instances will be charged by the second. Similarly, you can also set a policy to remove instances from the scaling group when the CPU utilization is low. If your load changes are predictable, you can set a scheduled task to plan your scaling activities.
The new instances can also be directly associated with the existing cloud load balancer (CLB) to share the distributed traffic of the scaling group and to improve service availability. You can also send an alarm to Admin to keep an eye on any exceptions.
Cumbersome manual operations are needed
The resources are subject to manual creation and termination. The CLB needs to be configured manually. Manual operation is error-prone, which may affect the business.
Cost Saving
Appropriate scaling of instances reduces costs
AS helps you maintain an optimal number of instances in response to changing business demands. AS launches new CVM instances seamlessly and automatically when demand increases, and terminates unneeded CVM instances automatically when demand decreases. This improves device utilization and reduces the costs of deployment and instances.
Idle resources result in waste
Extra CVMs need to be reserved to ensure the application always has enough capacity to meet demand.
Fault Tolerance
AS automatically monitors the health of instances
AS detects any unhealthy instance, and automatically replaces it with a new one. This ensures that your application is getting the desired computing capacity so that your business can run normally and smoothly.
Unhealthy instances are exposed to delayed processing
Unhealthy instances are not replaced until the business interruption is discovered, which compromises business availability.    
﻿

ヘルプとサポート

この記事はお役に立ちましたか？

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

Benefits	With Auto Scaling	Without Auto Scaling
Automatic	Automatically scale instances without manual interventionAuto Scaling (AS) automatically and dynamically adds or removes CVM instances in real time based on the business load, ensuring that you are running the optimal number of instances without manual intervention. For example, you can set a scaling policy to add CVM instances to the scaling group when the CPU utilization is high, and the new CVM instances will be charged by the second. Similarly, you can also set a policy to remove instances from the scaling group when the CPU utilization is low. If your load changes are predictable, you can set a scheduled task to plan your scaling activities. The new instances can also be directly associated with the existing cloud load balancer (CLB) to share the distributed traffic of the scaling group and to improve service availability. You can also send an alarm to Admin to keep an eye on any exceptions.	Cumbersome manual operations are needed The resources are subject to manual creation and termination. The CLB needs to be configured manually. Manual operation is error-prone, which may affect the business.
Cost Saving	Appropriate scaling of instances reduces costs AS helps you maintain an optimal number of instances in response to changing business demands. AS launches new CVM instances seamlessly and automatically when demand increases, and terminates unneeded CVM instances automatically when demand decreases. This improves device utilization and reduces the costs of deployment and instances.	Idle resources result in waste Extra CVMs need to be reserved to ensure the application always has enough capacity to meet demand.
Fault Tolerance	AS automatically monitors the health of instances AS detects any unhealthy instance, and automatically replaces it with a new one. This ensures that your application is getting the desired computing capacity so that your business can run normally and smoothly.	Unhealthy instances are exposed to delayed processing Unhealthy instances are not replaced until the business interruption is discovered, which compromises business availability.

tencent cloud

Auto Scaling

Strengths

ヘルプとサポート