Nikhil Reddy
Nikhil Reddy
Hi @HansScharrer For your scenario looks like the fix that you made will work.
@whoDoneItAgain Sorry about the issue, can you confirm if you are using the latest version of instance scheduler v1.4.0, which has the changes to ignore this error (i.e logs the...
@whoDoneItAgain I tried replicating the issue, I was able to see that the solution was generating the error message in the log files for the db instance within the cluster....
Hi @rseuchter The solution is currently compatible with Python3. Please refer to the latest version v1.4.0.
@gshetty437 1. Is the delete, modify and add expected, -- the delete section has resources that are currently not part of the latest version of the solution i.e the solution...
Hi @skrishna-dhcs Can you provide more information regarding this? Like should the instance be started and kept in Started state indefinitely or should the instance be started after 30 days...
Hi @emmanueldiquas This issue has been identified and will be fixed in the next release. Similar issue [240](https://github.com/awslabs/aws-instance-scheduler/issues/240)
@phlrnnr Thanks for the feedback we will review the documentation and make the updates accordingly.
@abjoerne Thanks for the feedback, we will review AWS Systems Manager Change Calendar and add a feature to the solution backlog.
@stuartpittaway The descriptions has been updated in the version 1.4.0