-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
Hudson v1.348 and Hudson Amazon EC2 plugin v1.6
I'm fairly certain that the EC2 private key is not required to launch an AMI - just the access key and secret key. I think it would be useful (and more secure for users) to allow us to add an ssh private key that's not necessarily the EC2 key. Of course this would only help those who are launching AMIs that are made with the ssh key inserted, but I think most of us that use AMIs as hudson slaves make our own.
The overall question, I think, is why does the module restrict how it's used? Why should a user of this module not be allowed to log into their worker instances using any account and with any key they wish? I can't think of a programmatic reason, nor a functional one. Hudson itself has no restriction, why does the module?
Of course, the fair response is "this is open source - feel free to fix it yourself". And it is fair, unfortunately, I'm allergic to java and have a doctors note saying so.
Greg