Cloud Server Auto Scaling Configuration Guide: Elastically Handling Traffic Fluctuations

Auto Scaling is one of the core advantages of cloud computing. It automatically adjusts server count based on real traffic, ensuring performance while avoiding resource waste.

1. Core Concepts of Auto Scaling

1.1 Working Mode

Traffic Increase → Trigger Scale-Out → Add Instances → Load Decreases
Traffic Decrease → Trigger Scale-In → Remove Instances → Save Costs

1.2 Key Components

Component Description
Launch Template Defines instance configuration (AMI, instance type, security group)
Auto Scaling Group Logical collection managing a group of instances
Scaling Policy Defines rules for when to scale out or in
Cooldown Period Wait time after a scaling operation

2. AWS Auto Scaling Configuration

2.1 Create Launch Template

# Launch template configuration
AMI: ubuntu-22.04-lts
Instance Type: t3.medium
Security Group: web-sg
Key Pair: my-key
User Data:
  #!/bin/bash
  systemctl start nginx
  systemctl enable nginx

2.2 Create Auto Scaling Group

aws autoscaling create-auto-scaling-group     --auto-scaling-group-name web-asg     --launch-template LaunchTemplateName=web-template     --min-size 2     --max-size 10     --desired-capacity 2     --vpc-zone-identifier subnet-xxx,subnet-yyy

2.3 Dynamic Scaling Policies

# CPU-based scale-out policy
aws autoscaling put-scaling-policy     --auto-scaling-group-name web-asg     --policy-name cpu-scale-up     --scaling-adjustment 1     --adjustment-type ChangeInCapacity     --cooldown 300

# Corresponding CloudWatch alarm
aws cloudwatch put-metric-alarm     --alarm-name cpu-high     --metric-name CPUUtilization     --namespace AWS/EC2     --threshold 70     --period 120

3. Alibaba Cloud Elastic Scaling

3.1 Configuration Steps

  1. Create a scaling group
  2. Configure scaling configuration (image, specification)
  3. Set scaling rules
  4. Create scheduled tasks or alarm tasks

3.2 Scaling Rule Examples

Rule Name: cpu-scale-out
Trigger Condition: CPU utilization > 75% for 5 consecutive minutes
Action: Add 1 instance
Cooldown: 300 seconds

Rule Name: cpu-scale-in
Trigger Condition: CPU utilization < 30% for 10 consecutive minutes
Action: Remove 1 instance
Cooldown: 600 seconds

4. Best Practices

Practice Description
Set min/max instance count Prevent infinite scaling
Multi-AZ deployment Improve availability
Connection warm-up Warm up new instances before adding to LB
Capacity buffer Reserve 20-30% buffer capacity
Regular testing Simulate traffic spikes to validate scaling strategies