Oracle Cloud Infrastructure Documentation

Creating Schedules

You can use Resource Scheduler to create schedules, add resources, dates, start and end times, and to review and edit the schedule before creating it. It includes instructions to complete the following tasks.

Required policies
Note

Important! To create and manage resource schedules, you must have permission to create a schedule (see Example 1) AND you must create a policy to allow a schedule to manage resources (see Example 2).

Example 1. This policy gives users permission to manage (create, delete, activate, and others.) resource schedules in their tenancy.

General example
Allow group <groupname> to manage resource-schedule-family in tenancy

Specific example
Allow group ResourceScheduleAdmins to manage resource-schedule-family in tenancy

Example 2. This policy gives a resource schedule permission to perform an action on a resource.

When a resource schedule is created, by default, it doesn't have permission to perform the action on target resources, so you must give it permission.

This policy allows a schedule to manage predefined resources such as instances in a compartment.

General example
Allow any-user to manage <resource_type> 
in compartment id <compartment_ocid> where all
{request.principal.type='resourceschedule',
request.principal.id='<ocid_of_resourceschedule>'}

Specific example
Allow any-user to manage instance in
compartment id ocid.compartment.oc1...q7fa where all
{request.principal.type='resourceschedule',
request.principal.id='ocid.resourceschedule.oc1.iad.axgr...dt8zb'}
Note

For more information, see Authentication and Authorization and Resource Scheduler Policies.

Resource Limitations

Resource Scheduler can process only 25 resources per schedule. If you select Dynamic, Resource Scheduler adds the first 25 resources it sees in the queue. You cannot select them or set the order of the resources. If you create a second schedule and select Dynamic, Resource Scheduler adds the same set of 25 resources that it did before. To process the rest of the resources, create a new schedule, select Static resources, and add them manually.

Task Overview

  1. Enter basic information (schedule name, description, action, and (optionally) tags.
  2. Select a compartment and resources.
  3. Create a schedule for the selected resources.
  4. Review and create the schedule
  5. Monitor and manage schedules (edit, disable, enable, delete, as needed)

Authentication and Authorization

This page describes the Identity and Access Management IAM process that is used to ensure secure access to Resource Scheduler.

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).

An administrator in your organization needs to set up groups , compartments , andpolicies  that control which users can access which services, which resources, and the type of access. For example, the policies control who can create new users, create and manage the cloud network, launch instances, create buckets, download objects, and so on. For more information, see Getting Started with Policies. For specific details about writing policies for each of the different services, see the Policy Reference.

Example policy

Allow the ResourceScheduleAdmins group to perform administrative operations with resource schedules, including Create, Update, Move, and Delete.

Allow group ResourceScheduleAdmins to manage resource-schedule in tenancy
Note

More policy examples are shown in Example Policies

If you are a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you should be using.

To use any of the Resource Scheduler API operations, you must be authorized in an IAM policy. If you're not authorized, contact the administrator. If you're an administrator who needs to write policies to give users access, see Getting Started with Policies.