ℹ️ Information: Scheduled Scaling enables you to configure your Auto Scaling Group to automatically adjust capacity based on predictable load changes. This approach is ideal for workloads with consistent patterns that occur at specific times daily, weekly, or seasonally.
Since we’ve already configured our load testing environment in the previous section, we’ll continue using those settings for consistency in our comparison of scaling methods.
To implement scheduled scaling:


Rush hour
⚠️ Warning: The Desired capacity, Min, and Max parameters will override the corresponding ASG settings during the scheduled period. When implementing multiple scaling types in production, carefully consider how these values interact with other scaling policies.
After successful creation, you’ll see your scheduled action in the list:

For effective testing:


To evaluate the effectiveness of scheduled scaling:

💡 Pro Tip: In this example, you can see a CPU utilization spike between 14:30 and 14:40, which corresponds to when we initiated the load test. After the new instance was added by the scheduled action, the load was distributed, resulting in the subsequent decline.

This granular view clearly shows how the scheduled scaling action affected system performance.
ℹ️ Information: Scheduled Scaling is particularly valuable for applications with predictable usage patterns:
🔒 Security Note: While scheduled scaling helps optimize resource utilization, it’s important to maintain minimum capacity levels that can handle unexpected traffic surges or potential DDoS attacks outside of scheduled scaling periods.
Scheduled Scaling provides a proactive approach to capacity management for workloads with predictable patterns. However, for maximum resilience and cost efficiency, AWS recommends combining scheduled scaling with other scaling types:
This multi-layered approach ensures your application remains responsive while optimizing resource utilization and cost.