The EC2 plugin requires launching slaves via SSH for on-demand instances. Due to various connectivity issues that have been reported with the SSH slaves plugin (and which I am experiencing constantly), I'd like to use an AMI that does its own connection to Jenkins master based on EC2 user-data.

The only change needed to support this would be a configuration option that allows me to tell the plugin to treat the on-demand instances like spot instances in terms of launching the Jenkins slave.