Why auto scaling matters in AWS - Performance Analysis

Time Complexity: Why auto scaling matters

O(n)

Understanding Time Complexity

We want to understand how the work needed to handle growing traffic changes when using auto scaling.

How does the number of servers and their management grow as demand increases?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

# AWS Auto Scaling example
aws autoscaling create-auto-scaling-group --auto-scaling-group-name my-asg \
  --launch-configuration-name my-launch-config --min-size 1 --max-size 10 \
  --desired-capacity 1 --vpc-zone-identifier subnet-12345

aws autoscaling put-scaling-policy --auto-scaling-group-name my-asg \
  --policy-name scale-out --scaling-adjustment 1 --adjustment-type ChangeInCapacity

# When CPU > 70%, scale out by 1 instance
# When CPU < 30%, scale in by 1 instance

This sequence sets up an auto scaling group that adds or removes servers based on CPU load.

Identify Repeating Operations

• Primary operation: Launching or terminating EC2 instances as load changes.
• How many times: Depends on how often load crosses thresholds, up to max-size times.

How Execution Grows With Input

As demand (load) grows, the number of instances increases one by one until the max limit.

Input Size (Load Level)	Approx. Instances Running
Low (10%)	1 (minimum)
Medium (50%)	5 (half max)
High (90%)	10 (max)

Pattern observation: The number of instances grows roughly linearly with demand until the max limit.

Final Time Complexity

Time Complexity: O(n)

This means the number of servers and scaling actions grows linearly as demand increases.

Common Mistake

[X] Wrong: "Auto scaling instantly adds all needed servers at once regardless of demand."

[OK] Correct: Auto scaling adds or removes servers step-by-step based on policies and thresholds, not all at once.

Interview Connect

Understanding how auto scaling grows with demand shows you can design systems that handle traffic smoothly and efficiently.

Self-Check

"What if the auto scaling group had no max size limit? How would the time complexity change?"

Practice

1. Why is auto scaling important in cloud infrastructure?

easy

A. It automatically adjusts the number of servers to match demand.

B. It manually requires admins to add servers during traffic spikes.

C. It reduces the need for backups and data recovery.

D. It guarantees zero downtime without any configuration.

Solution

1. Step 1: Understand auto scaling purpose

   Auto scaling automatically changes server count based on demand to keep apps running smoothly.

2. Step 2: Compare options

   Only It automatically adjusts the number of servers to match demand. describes automatic adjustment. Others describe manual work, unrelated features, or guarantees that are not true.

3. Final Answer:

   It automatically adjusts the number of servers to match demand. -> Option A

4. Quick Check:

   Auto scaling = automatic server adjustment [OK]

Hint: Auto scaling means automatic server count changes [OK]

Common Mistakes:

• Thinking auto scaling is manual
• Confusing auto scaling with backups
• Assuming zero downtime without setup

2. Which AWS service is used to set up auto scaling for EC2 instances?

easy

A. AWS Lambda

B. AWS CloudTrail

C. Amazon EC2 Auto Scaling

D. Amazon S3

Solution

1. Step 1: Identify service for auto scaling EC2

   AWS provides a specific service called Amazon EC2 Auto Scaling to manage scaling of EC2 instances.

2. Step 2: Eliminate unrelated services

   AWS Lambda runs code, S3 stores files, CloudTrail logs activity. None handle auto scaling EC2.

3. Final Answer:

   Amazon EC2 Auto Scaling -> Option C

4. Quick Check:

   EC2 auto scaling service = Amazon EC2 Auto Scaling [OK]

Hint: EC2 auto scaling uses Amazon EC2 Auto Scaling service [OK]

Common Mistakes:

• Confusing Lambda with auto scaling
• Choosing storage or logging services
• Not knowing specific auto scaling service

3. Given this auto scaling policy: scale out when CPU > 70%, scale in when CPU < 30%. If CPU usage is 75%, what happens?

medium

A. The number of servers increases.

B. The number of servers decreases.

C. No change in server count.

D. The servers are replaced.

Solution

1. Step 1: Analyze the scale out condition

   The policy says to add servers when CPU usage is above 70%. CPU is 75%, so condition is met.

2. Step 2: Determine action

   Since CPU is high, auto scaling will increase server count to handle load.

3. Final Answer:

   The number of servers increases. -> Option A

4. Quick Check:

   CPU > 70% triggers scale out = increase servers [OK]

Hint: High CPU triggers scale out (add servers) [OK]

Common Mistakes:

• Confusing scale out with scale in
• Thinking servers are replaced automatically
• Assuming no change on high CPU

4. You set an auto scaling policy but notice your app still crashes during traffic spikes. What is a likely cause?

medium

A. The app does not need more servers during spikes.

B. Auto scaling automatically fixes all crashes without setup.

C. Auto scaling only works for storage, not servers.

D. The scaling policy thresholds are set too high, delaying scaling.

Solution

1. Step 1: Understand scaling delay impact

   If thresholds are too high, scaling triggers late, causing crashes during spikes.

2. Step 2: Eliminate incorrect options

   Auto scaling needs proper setup, does not fix all crashes automatically. It works for servers, not just storage. App likely needs more servers during spikes.

3. Final Answer:

   The scaling policy thresholds are set too high, delaying scaling. -> Option D

4. Quick Check:

   High thresholds delay scaling = crashes [OK]

Hint: Check if scaling thresholds are too high [OK]

Common Mistakes:

• Assuming auto scaling fixes crashes automatically
• Thinking auto scaling only manages storage
• Ignoring app server needs during spikes

5. You want to optimize costs by scaling down servers during low traffic but avoid frequent scaling actions. Which approach is best?

hard

A. Set aggressive scale-in thresholds with short cooldown periods.

B. Use moderate scale-in thresholds with longer cooldown periods.

C. Disable scale-in to keep servers always running.

D. Manually add and remove servers daily.

Solution

1. Step 1: Understand cost optimization and stability

   To save costs, scale down servers when traffic is low but avoid too frequent scaling to prevent instability.

2. Step 2: Evaluate options

   Aggressive thresholds and short cooldown cause frequent scaling (not good). Disabling scale-in wastes money. Manual scaling is inefficient. Moderate thresholds with longer cooldown balance cost and stability.

3. Final Answer:

   Use moderate scale-in thresholds with longer cooldown periods. -> Option B

4. Quick Check:

   Moderate thresholds + longer cooldown = cost and stability [OK]

Hint: Balance thresholds and cooldown for cost and stability [OK]

Common Mistakes:

• Setting too aggressive scale-in causing flapping
• Disabling scale-in wastes money
• Relying on manual scaling