Scheduled Scaling
Start course
2h 49m

This section of the Solution Architect Associate learning path introduces you to the core computing concepts and services relevant to the SAA-C03 exam. We start with an introduction to the AWS compute services, understand the options available and learn how to select and apply AWS compute services to meet specific requirements. 

Want more? Try a lab playground or do a Lab Challenge

Learning Objectives

  • Learn the fundamentals of AWS compute services such as EC2, ECS, EKS, and AWS Batch
  • Understanding how load balancing and autoscaling can be used to optimize your workloads
  • Learn about the AWS serverless compute services and capabilities

The final bit of scaling that we should mention is time based or scheduled scaling. Scheduled scaling is when you add or remove instances from your auto scaling groups based on certain time parameters. For example, you might have a fleet of batch processing instances that you only want to go online during the middle of the night when spot instance prices are generally lower. You can have a scheduled scaling mechanism set in place to load up on these instances and get your work done during those specific hours. Scheduled scaling is a great way to help reduce costs by setting time periods in which your architectures run.

Another example is using scheduled scaling to turn off your dev environments after business hours have concluded. Why would you want to have any extra instances running when they don't need to be. With scheduled scaling you can turn off all of those test and dev workloads when they are not being used, and simply schedule them to turn back on in the morning.

And you can still have combinations of these scaling mechanisms working together. Maybe you have your dev and test environments set to turn on and off at night, but during the day, they can use dynamic scaling to increase the number of instances when needed, and tune back down to a minimum requirement when no tests are being performed.

Using scheduled scaling can save you quite a bit of money if you are able to work it into your architectures. It works especially well when you have harnessed the power of spot instances, which does require some allowances from your solution - like being able to handle stopping and starting.


About the Author
Learning Paths

Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data center and network infrastructure design, to cloud architecture and implementation.

To date, Stuart has created 150+ courses relating to Cloud reaching over 180,000 students, mostly within the AWS category and with a heavy focus on security and compliance.

Stuart is a member of the AWS Community Builders Program for his contributions towards AWS.

He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.

In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.

Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.