# Scheduler DuploCloud allows you to automatically shut down Tenant resources, such as EC2 instances and RDS databases, based on defined schedules. Auto Scaling Groups (ASGs) and RDS clusters (Aurora or multi-instance clusters) are not supported. This feature is available only for AWS. It is useful for managing costs and conserving resources in development, test, or other non-production environments. To schedule shutdowns for instances in a Tenant, complete these three steps: 1. **Define Periods**: Define specific time ranges and days of the week when shutdowns should occur. 2. **Create Schedules**: Group one or more periods and apply them to a particular resource type (EC2 or RDS). 3. **Assign Schedules**: Assign the schedules to all instances of a resource type in the Tenant or to specific individual instances. Schedules can be either: * **Group schedules:** Apply to all instances of the selected resource type in a Tenant * **Individual schedules**: Apply only to the selected instance(s) (EC2 or RDS) {% hint style="info" %} **Notes:** * Each Tenant can have one Group and one Individual schedule per resource type (EC2 or RDS). * You can create and use multiple schedules per Tenant. {% endhint %} ## Prerequisites Before you can configure instance schedules, you must first enable the feature in **System Settings**. 1. Navigate to **Administrator** -> **System Settings.** 2. Select the **System Config** tab. 3. Click **Add**. The **Add Config** pane displays.

4. In the **Config Type** list box, select **Flag**. 5. In the **Key** field, select **Enable Instance Scheduler**. 6. In the **Value** list box, select **True**. 7. Click **Save**. The **Scheduler** tab will display when viewing any Tenant under **Administrator** -> **Tenants**. {% hint style="info" %} It may take up to 10 minutes after saving before the **Scheduler** tab becomes visible under **Administrator → Tenants**. {% endhint %} ## Creating Shutdown Periods A **Period** defines the time window and days of the week when a shutdown should occur. Once created or edited, periods can be reused across multiple schedules. DuploCloud provides several predefined periods, including **office-hours**, **working-days**, and **weekends**, to help you get started quickly. You must edit them to set the appropriate days and start/end times for your environment. You can also create your own custom periods if the defaults don't match your needs. To add or edit a period: 1. Navigate to **Administrator** -> **Tenants**. 2. Select the name of the Tenant from the **NAME** column. 3. Select the **Scheduler** tab. 4. In the **Periods** section, click **Add**. The **Add Period** pane displays.

5. Complete the following fields:


Name	Enter a unique name for the period (e.g., `weeknights-7pm`).
Begin Time	Enter the start time in HH:MM format (e.g., `19:00`).
End Time	Enter the end time in HH:MM format (e.g., `07:00`).
Weekdays	Select the days of the week when the shutdown should occur.
Description	Optionally, enter a description for this period for internal reference.

6. Click **Save**. ## Creating a Schedule Schedules define how and when shutdown periods are applied to a specific resource type within a Tenant. You can create two types of schedules: * **Group schedules:** Applies to all EC2 or RDS instances in the Tenant * **Individual schedules:** Applies only to the specific EC2 or RDS instances selected **Multiple schedules per Tenant are supported**, but only one active Group and one Individual schedule per resource type can be assigned at a time. 1. Navigate to **Administrator** -> **Tenants**. 2. Select the name of the Tenant from the **NAME** column. 3. Select the **Scheduler** tab. 4. In the **Schedule** section, click **Add**. The **Add Schedule** pane displays.

5. Complete the fields as shown in the following table.


Name	Enter a unique name for the schedule (e.g., `dev-ec2-weeknights`).
Resource Type	Select EC2 or RDS. This determines which type of instances the schedule applies to. Schedules are scoped to a single resource type. You must create separate schedules for EC2 and RDS instances.
Scheduler Type	Choose how the schedule should be applied: • Group: Applies the schedule to all instances of the selected resource type within the Tenant. • Individual: Applies the schedule to only the specific instances you choose later during assignment.
Periods	Select one or more previously defined periods. These determine the time ranges and days the schedule will be active.
Timezone	Select the time zone the schedule should use.
Description	Optionally, enter a description for this schedule.

6. Click **Save**. It may take a few minutes before the created schedule appears as a selectable option when assigning schedules to instances. 7. Repeat steps 1-6 to add additional schedules to a Tenant. {% hint style="info" %} **Schedule Behavior Summary** * **Group** schedules apply to *all EC2 or RDS instances* in the Tenant and do **not** require selecting instances during assignment. * **Individual** schedules apply only to the *specific instances* you select during assignment. * If a resource has **both** a Tenant and an Individual schedule assigned, the **Individual schedule takes precedence**. {% endhint %} ### Assigning a Schedule to Instances After creating one or more schedules, the final step is to assign them to resources in the Tenant. You can choose to: * Assign a schedule you’ve already created (Group or Individual), or * Select **None** to ensure that no schedule is applied to the selected instances. This is useful when you want certain instances to remain running at all times, even if a Tenant-level (Group) schedule is in effect. To assign a schedule, follow these steps: 1. Navigate to **Administrator** -> **Tenants**. 2. Select the name of the Tenant from the **NAME** column. 3. Select the **Scheduler** tab. 4. In the **Schedule Assignment** section, click **Add**. The **Assign Schedule** pane displays.

5. Complete the following fields.


Instance Type	Select the resource type (EC2 or RDS). This filters which schedules and instances are shown.
Assign Schedule	Choose one of the created schedules. Only schedules that match the selected resource type will appear. You can also select None to explicitly remove any assigned schedule from the selected instance(s). This is useful if you want an instance to always remain running, even if a Tenant-wide schedule exists.
Instances	- For Individual schedules: Select the instances you want to apply the schedule to. - For Group schedules: The instance list will be disabled and the schedule will apply to all instances of the selected type automatically. Note: If a resource has both a Tenant and an Individual schedule assigned, the Individual schedule takes precedence.

6. Click **Save**. {% hint style="info" %} The scheduler runs on AWS’s standard schedule interval, which checks for updates every 5 minutes, therefore it may take up to 5 minutes for the schedule to take effect. {% endhint %}