#Time zones scheduler windows#

Greater than 10 minutes, the scheduler will start the instance the same number of minutes as Start the instance 10 minutes before the maintenance window. If you set theįrequency AWS CloudFormation parameter to 10 minutes or less, the solution will This solution uses the AWS Lambda frequency you specified during initial configuration toĭetermine how long before the maintenance window to start your instance.

Run, the maintenance window changes will only be picked up by the lambda any time between For example, if you selected a frequency of 5 minutes for the scheduler lambda to Of the SSM maintenance window, the changes are picked up at the next scheduled run of the Once the SSM Maintenance window is created and the schedule is configured with the name Other running period specifies that the instance should run, and if the maintenance event is The maintenance window and stop the instance at the end of the maintenance window if no To schedule your Amazon EC2 instances, the solution will start the instance before the start of When you specify the name ofĪ maintenance window that exists in the same account and AWS Region as your deployed stack The ssm-maintenance-window field allows you to automatically add anĪWS Systems Manager maintenance window as a running period to a schedule.

SSM maintenance window field (only applies to EC2 instances) Started before 9 AM, the solution will not stop the instance at 5 PM. For example, if an instance with a period that runs from 9 AM to 5 PM is manually The end of a running period if the instance was manually started before the beginning of the The retain_running field prevents the solution from stopping an instance at

If this field is set to true, it also restarts an instance if it was manually stopped during a running period. If this field is set to true and a user manually starts an instance outside of a running period, the solution will stop the instance. Schedules contain an enforced field that allows you to prevent an instance from being manually started outside of a running period, or manually stopped during a running period. On-Demand Instance or Spot Instance in the Amazon EC2 User For more information, refer to Hibernate your If you set the solution to use hibernation, but your instances are not configured for hibernation or they do not meet the hibernation prerequisites, the solution logs a warning and the instances are True, instances are hibernated instead of stopped when the solution stops

Hibernation saves the contents from the instance memory (RAM) to yourĪmazon Elastic Block Store (Amazon EBS) root volume.

#Time zones scheduler windows#

For more information, refer to Supported Linux AMIs and Supported Windows AMIs in the Amazon EC2 User If this field is set to true, your EC2 instances must use an Amazon Machine Image The hibernate field allows you to use hibernation for stopped Amazon EC2 List of acceptable time zone values, refer to the TZ column of the List of tz database The schedule will use the default time zone you specify when you launch the solution. You can also specify a time zone for the schedule. Used in a schedule, Instance Scheduler on AWS will apply the appropriate start action whenĪt least one of the periods is true. Should run, and a schedule can contain more than one period. PeriodsĮach schedule must contain at least one period that defines the time(s) the instance Each schedule must have a unique name, which is used as the tag value that identifies the schedule you want to apply to the tagged resource. Schedules specify when Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Relational Database Service (Amazon RDS) instances should run.