Hello @npalm @gertjanmaas @mcaulifn

I have changed the instance_initiated_shutdown_behavior to stop( https://github.com/philips-labs/terraform-aws-github-runner/blob/master/modules/runners/main.tf#L64) and created all the resources and configured the idle config for our runner instance.

So my github runner configuration has the following values:
idle_config = [{
cron = "* * 9-17 * * *"
timeZone = "America/New_York"
idleCount = 2
}]

• minimum_running_time_in_minutes = "35"
• Maximum runner instance is set to 3

I have triggered like 30 github actions and scale up lambda created 3 ec2 instances and completed all 30 github actions.

since I had IdleCount as 2 After 35 minutes the 3rd ec2 instance should have stopped based on the instance_initiated_shutdown_behavior values, but instead that 3rd ec2 instance got terminated.

• Whenever so many github actions are created, looking for options to avoid terminating/spinning up new instances.
• Do we have any way to stop/start the runner instance instead of terminating them whenever more github actions are triggered?
• Is there any way to stop/start github runner instance ?

Please let me know if you need more information.