Schedules

Overview

Schedules are how you instruct the engine what resource types are being scheduled, when they’re being scheduled (periods), and what changes will be made during the schedule.

The scheduling engine supports 4 types of resources.

Defining a schedule will allow you to select a resource type, then apply periods to your schedule to change instance type, concurrency, resource allocation, or other attributes related to the resource AWS resource chosen.

Introduction

Schedules are the main part of this engine. They are comprised primarily of periods which define when the schedule is active. Along with periods schedules will also define default values (if applicable) for the state of resources using the schedule when the schedule is not active.

When a resource is within a Start and End time period, this means the resource will be “Active” and will be running. When a resource is outside of the Start and End time period the resource will be “Inactive” and will be turned off (EC2), or scaled down according to the schedule for Labmdas, RDS, ASGs.

Usage

Define a schedule

When defining a schedule (see creating schedules) you specify a Schedule Name. This will be the value you put in the schedule tag you’ve configured for your AWS account.

The next field is the schedule type, here you specify the resource type you want this schedule to apply to. A schedule can only act on one resource type.

Additionally you can set the timezone for the schedule. We suggest choosing your own timezone when creating schedules to make it easier and prevent any accidental timezone conversion mishaps.