Scheduled Scaling Actions
What you'll learn: How to use time-based schedules to automatically adjust your infrastructure capacity before predictable traffic arrives.
The Core Idea
Scheduled Scaling Actions let you preemptively scale your infrastructure based on the calendar and clock—not just reactive metrics. Instead of waiting for CPU to spike at 9 AM every Monday, you tell Auto Scaling: "Add 10 servers every weekday at 8:45 AM, remove them at 6 PM."
This is proactive scaling rather than reactive. You're preparing for known traffic patterns ahead of time.
Why Scheduled Actions Matter
Many applications have predictable usage patterns:
- E-commerce sites see morning shopping rushes
- Business apps are busy during work hours, quiet at night
- Gaming platforms peak on weekends
- Batch jobs run at specific times daily
With scheduled actions, you avoid the lag time between traffic arriving and Auto Scaling reacting. Your capacity is already there when users show up.
How It Works
You create a schedule that specifies:
- When to execute (specific time, recurring pattern, cron expression)
- What capacity to set (minimum, maximum, and/or desired capacity)
- Which Auto Scaling group to modify
For example: "Every Monday at 8:00 AM UTC, set desired capacity to 20 instances." At that exact time, Auto Scaling adjusts capacity—no metrics required.
Think of It Like This
Imagine you run a coffee shop. Scheduled scaling is like hiring extra baristas for the morning rush before customers arrive—not scrambling to call someone in after the line is already out the door.
Key Takeaway: Scheduled Scaling Actions use time-based triggers to adjust capacity proactively for predictable traffic patterns, ensuring resources are ready before demand arrives.