|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Seems to me the way to do this is to take the private key given and then upon startup feed it via the user-data to the authorized_keys file of the ec2-user.
ie:
#!
echo ssh-rsa AAAB3N...QcGskx keyname >> ~ec2-user/.ssh/authorized_keys
echo ssh-rsa BBRdt5...LguTtp another-key >> ~ec2-user/.ssh/authorized_keys
From: http://stackoverflow.com/a/13202445
Regardless, the plugin still needs an keypair to launch the instance so I feel like this is a won't implement feature and your workaround is as described.
Edit (again![]()
. So yes EC2 doesn't need a keypair to launch an instance, just your access keys.
Thinking about it even more, I'm going to change my opinion here. The plugin could instead, if it doesn't find the keypair match on EC2 to automatically submit the public key to the authorized_keys for the user specified. That could implement this feature.