Close this search box.

Cloud task scheduler

The primary function of the cloud task scheduler is to automate the execution of repetitive tasks, gaining productivity and saving money.

It is currently possible to schedule the following tasks for your cloud servers:

  • Backup  (EC2 and RDS)  – the scheduler will create an image of the server. Creating an image is equivalent to creating a backup, as this image can be transformed into a server at any time. To perform the backup, Amazon reboots the server to ensure the integrity of the data on the disks. It is also possible to define the retention policy at this point (such as whether or not Cloud8 will purge an old backup);
  • Copy to another region (EC2 and RDS)  – after the backup, it is possible to define whether the backup will be copied to another region. Used for Disaster Recovery purposes;
  • Upgrade/downgrade (EC2 and RDS)  – the scheduler will upgrade or downgrade the server type. It is also possible to choose whether the server will have conventional disks or disks with optimized I/O (EBS Optimized). Example: a server that is m1.large + I/O optimized during the day, can become an m1.small at night. For this type change to be made, Amazon reboots the server. In the case of RDS, it is still possible to turn MultiAZ/SingleAZ on/off, saving 50%.
  • Start the server  – the scheduler will start the server and connect the Elastic IP already associated with it. If the server does not have an Elastic IP, it will gain a dynamic IP;
  • Stop Server  – The scheduler will stop the server. You can also choose the ‘Force stop’ option. The difference is that Amazon, in the first case, tries to give a soft ‘shutdown’, but if there is a process that refuses to terminate, the server can remain in the ‘shutdown’ state indefinitely. ‘Forcing’ would be equivalent to unplugging and literally turning off the server;
  • Connect to a Load Balancer ;
  • Disconnect from a Load Balancer .

The frequency of appointments can be simple or advanced. We support:

  • Daily: every day, weekends or weekdays
  • Weekly: combination of days of the week. Ex: Monday and Thursday, etc.
  • Monthly: specific day of the month, first Monday of the month, last day of the month

Main use cases

Creativity is the limit, but there are some more common scenarios where customers are already benefiting:

  • Backup  – sleep easy. Schedule the creation of your backups every morning and receive an email that everything worked well;
  • Savings  – if your system/blog/site is used less at the weekend, why not ‘downsize’ and save money? Example: from Friday to Saturday you can transform a ‘large’ server to ‘small’ and on Monday morning return it to ‘large’! You can achieve savings of over 30% on your bill!
  • Development environment  – ​​why leave a development environment on all the time? If it is only used during business hours, create schedules to turn it off during the week and on the weekend. You can achieve savings of 60% on your bill!
  • Scheduled peaks  – with customized schedules such as “Last Thursday of the month” it is possible to schedule a server upgrade to run a demanding process. Example: a payroll application or a television campaign that needs to boost the capacity to receive simultaneous accesses;
  • Forgetfulness  – that’s right, for forgetful people :). How many times have you forgotten a server was turned on and after 2 weeks you noticed that your bill had almost doubled? If you create a preventive schedule to stop the server, you will no longer have surprises at the end of the month.