Issue with Maintenance Window Feature - Instances Not Stopping

Good Morning,

Thank you for the work put into the project, it has been a great aid in our deployment.

We are keen to use the maintenance window feature to aid in patch management but are coming up against some issues.

The scheduler seems to create the schedules on-the-fly each time instance scheduler is invoked.

You can see the schedules created in the logs as expected.

2020-11-16 - 09:10:46.600 - INFO    : Created schedule testmw from SSM maintence window, start is 2020-11-16T08:05:00+00:00, end is 2020-11-16T09:15:00+00:00

In this example, after 09:15 when the server should shut down the next schedule is generated instead, so the stop date from the previous schedule never occurs:

2020-11-16 - 09:15:47.337 - INFO    : Created schedule testmw from SSM maintence window, start is 2020-11-16T08:05:00+00:00, end is 2020-11-16T09:15:00+00:00

Not sure if this is a bug or if we are doing something wrong, many thanks for any help

[praveenis]

Thanks @andycattle for sharing the details. As I told before we have some limitation and defects using Maintenance window feature. We have this item in our backlog for future release to improve the usability of the feature.

[praveenis]

Hi @andycattle ,

Instances will be started based on the Frequency Interval specified in the Input parameter of the solution stack.

If the Frequency Interval is less than 10, Instances will be started 10 mins before the maintenance window and stopped at the end of maintenance window.

If the Frequency Interval is greater than 10, It will use Frequency interval value to start the maintenance window. for example, if Interval specified is 30, Instances will be started 30 mins before the maintenance window.

Also below are the limitation with Instance Scheduler.

1. Maintenance window must exists in the same account and AWS Region as your deployed stack to schedule your Amazon EC2 instances
2. Maintenance window created must use UTC time format.

Please let us know if this helps. Also can you please confirm the version of the Instance Scheduler deployed is latest.

Thanks, Praveen