[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title John La Barge commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key This feature is needed for me too. Enterprises do not allow access to pem files generally. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135942.126782350.13427.1587165660682%40Atlassian.JIRA.
[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title Franklin Ye commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key Forked v1.40 and removed the Generate Key button to use SSH Private Key. Click here to try it out. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title Gregory Brauer commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key We had already been using manually launched EC2 instances using the built-in ssh credentials management to log into a "jenkins" account using a dedicated ssh key. I just want to be able to select one of my existing ssh credentials in the Amazon EC2 plugin so that it would work just like the normal ssh agent configuration, but there is no way to do this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Title: Message Title Ben Jones commented on JENKINS-5853 Re: Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key I apologize for bringing such an old topic back up, but I encountered an issue related to this today. The problem I see is that jobs being run on an EC2 slave are able to obtain root privileges on that slave. This may be just fine for some setups, but it obviously has the potential to introduce quite a bit of irritation and chaos (or worse) as well. To prevent this, I would like to have the master connect to an ec2 slave using the configured remote user, but with a key separate from that which the instance was launched with. Using a base Ubuntu image as an example, I'm currently restricted to using 'ubuntu' as the remote user and connecting with the key the instance was launched with. Instead I would like to connect as 'jenkins' with some other key entirely (the assumption is that I created this user appropriately via user data, pre-baked ami, etc.). I could just generate an authorized_keys entry for that user by generating a public key from the private key, which I suppose is just fine, but it doesn't seem like an intuitive solution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Nick Robinson-Wall commented on JENKINS-5853 Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key +1 for this. When I create my AMIs for Jenkins it has the same built-in 'ci' user as my non-ec2 slaves - configured using puppet. I would be fine with simply importing my existing public key into AWS and giving the contents of the private key to the ec2 plugin, but see JENKINS-15389 for why this is not possible. 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
