Errors: Request was not handled, no handler was able to handle this type of request about instance-scheduler-on-aws HOT 2 CLOSED

the easiest solution I would recommend is to:

-Use the default installation
-Create two schedules with names as below
-ec2-schedule -> start 9:00, stop 17:00
-rds-schedule -> start 8:50, stop 17:10
-Tag the ec2 and rds instances you want to control
-EC2 instances Schedule=ec2-schedule
-RDS instances Schedule=rds-schedule

RDS instance starts at 8:00, followed by ECS instances at 9:00.
ECS Instances stops at 17:00, followed by RDS instances at 17:10

from instance-scheduler-on-aws.

Thanks @arieleeuw
I happen to debug more to how/where the lambda handles request and in case of cloudwatch even handler there seems to be a issue with
scheduler logical id and how it parses or handles .
This is what I see where it's sort of hardCoded.
startswith("{}-SchedulerRule

So now my logicalIds are SchedulerRuleEC2/RDS instead of EC2/RDSSchedulerRule.
This basically works now, So Ive separated to two lambdas one for each service.

Earlier it was failing coz the cloudwatch events has its resource arn format ending with the name EC2SchedulerRule.

from instance-scheduler-on-aws.