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

Scenarios

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-08 17:53:29

Configuring scaling policy in advance

If you know when to scale out and scale in, you can set an Auto Scaling scheduling policy. At the corresponding time, the system will automatically add or remove a CVM instance, with no need for human efforts.

Coping with business volume surges with low costs

When the traffic arises, you need to prepare CVMs in advance to prevent CVM overload caused by the sudden surge in CPU utilization. When the traffic decrease, you need to reduce CVMs accordingly. With the Auto Scaling policy configured, the system will determine when to trigger scaling accordingly. When the monitoring metrics reach the threshold, then CVM instances are automatically added or removed, and Cloud Load Balancer configuration is automatically implemented. This reduces the cost for servers and also human efforts.

Replacing unhealthy CVMs automatically

To prevent your business from being affected by unhealthy CVMs, you need to constantly monitor the operation status of CVMs. With Auto Scaling, the system regularly performs health checks on CVMs. When the system detects an exceptional CVM instance, it automatically creates a new instance to replace the exceptional instance. You can check all the logs if necessary.

ヘルプとサポート

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

フィードバック