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 ScalingTutorialCreating Servers for Sending Requests

Creating Servers for Sending Requests

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-08-15 18:45:48

Scenario Description

Servers with active outbound access are primarily used to execute scheduled or event-driven external request tasks. These tasks have clear timeliness and do not require servers to run for a long time. Auto Scaling (AS) supports rapid expansion of servers for sending requests to dynamically adjust resources based on task requirements. For example, in an online education SaaS platform, background tasks need to be executed elastically when triggered by user clicks or advertisements, and tasks of an advertisement platform require automatic scaling based on user behavior to ensure response under high concurrency.


Usage

Requesting servers can be managed in scaling groups to achieve automated scaling. The steps are as follows:
1. Create a launch configuration: Select a model, images, storage, and other resources based on task requirements.
2. Create a scaling group and set the policy: Set the minimum capacity and maximum capacity to be within a range required for tasks.
Scheduled tasks should be prioritized for time-sensitive tasks.
An alarm-triggered policy can be added to handle sudden traffic.
3. Manage servers: Add existing Cloud Virtual Machine (CVM) instances to the scaling group, or set removal protection to protect core nodes.

Benefits from AS

Automation efficiency: Manual Ops is not needed, and the deployment time is reduced.
Cost optimization: Resources are used on demand to avoid long-term reservations.
High responsiveness: Rapid scaling is supported to process time-sensitive tasks.
Robustness guarantee: Abnormal nodes can be replaced automatically in case of failures or attacks.

Applicable Industries

Online education SaaS platforms
Advertising and media industries
E-commerce and finance
Data processing and rendering

Ajuda e Suporte

Esta página foi útil?

comentários