Hi Team,

We are experiencing an issue with the Jenkins EC2 plugin where EC2 instances are not being terminated after the job completes, even though the idle termination time has been exceeded.

Details:

• Plugin: Jenkins EC2 Plugin
• Issue: Instances remain running for 2-3 days after job completion.
• Expected Behavior: Instances should terminate after the configured idle termination time.
• Observed Behavior: Instances remain active beyond the idle threshold.
• Impact: Increased AWS costs due to unused EC2 instances running for extended periods.

Steps to Reproduce:

1. Configure Jenkins EC2 plugin with idle termination time set (e.g., X minutes).
2. Run a Jenkins job on an EC2 agent.
3. Observe that the instance remains running even after the job completes and idle time exceeds the configured threshold.

We are using latest version of ec2 plugin - 2029.v50458f410ef9

can someone help??