The Work Scheduler does have a few limitations to its functionality that are important to note and manage. Each are described below.
User Role Access Restrictions
In order to create and configure a Work Schedule, you must have one of the following user roles assigned: Admin, DevOps.
In order to view a Work Schedule, you must have one of the following user roles assigned: Admin, DevOps, Developer, Manager.
Users with the Accountant role assigned only are not able to view the Work Scheduler.
Only 'Controllable' Servers
The Work Scheduler requires that Aimably is connected to the AWS Account using the Data and Scheduling full service connection policy. Any server that is within an AWS Account that has been connected using the Usage Data Only restricted policy will not appear in the list for work scheduling.
If you would like to apply a Work Schedule to a server that is currently connected using the Usage Data Only policy, you will need to re-run the connection wizard for that AWS Account and apply a new policy.
For more information on AWS connection policies, please visit Selecting the Right AWS Policy for Your Business.
Future Servers Not Supported
The Work Scheduler only applies to servers that are provisioned at the time of the Work Schedule creation. By creating a Work Schedule, you authorize Aimably to turn on or turn off servers that apply to your subgroup selections at the time of creation. If a new server comes online in your AWS account that meets the criteria of your original Work Schedule, the server will not be controlled by the Work Schedule until you add it manually to the schedule.
Only Weekly Repeating Schedules
By definition, all Work Schedules are repetitive, recurring weekly events. Single-use events or events that recur under non-weekly schedules are not supported at this time. We recommend using the Manual Control module to perform these tasks.
Server Status of Stopped or Started Required for Execution
The Work Scheduler will only perform its action on a server if the server is currently in a Stopped or Started state. Any other AWS state, such a Terminated, Unavailable, Pending Start, etc., will result in the Work Scheduler not performing any actions.