Currently, We have one amazon account linked with the plugin with multiple AMI's for windows and Linux. We don't see any issue with Windows but for the Linux agent we are occasionally seeing the below problem. Our nodes are set to limit of 5 Uses.

Problem:

• Nodes are created as per when the resource is per the resource requirement.
• On a rare occasion, the Jenkins Coordinator creates a new Jenkins EC2 Agent, however the IP address assigned to the “Jenkins Worker Node” is the same as the Jenkins Coordinator IP address

Debugging:

• Looked at the AMI to verify all the versions are right and installed correctly. Looks good.
• Added more print statements to debug more like printing hostname and IP address.

Jenkins Master --> m4.4xlarge 

Linux Agent --> C5Large

Note: This happens occasionally sometimes 3 to 4 times a week. We even checked the load of the Jenkins Master to see if there is any pattern but found none.

Please let me know if you need anymore information from me.