-
Bug
-
Resolution: Unresolved
-
Critical
-
AWS EC2
Linux (Controller + Agents)
Windows (Agents)
Windows has a native port of OpenSSH since years now. Connecting to static Windows agents via SSH (SSH agent plugin) also works fine. But the EC2 plugin still insists on connecting through WinRM (which is a nightmare in itself) or requires the workaround of setting the type to "unix" (with all the implications this may have).
Please fix this bug.
[JENKINS-70093] EC2 Plugin does not allow SSH connection to Windows instances (natively)
Description |
Original:
Windows has a native port of OpenSSH since years now. Connecting to static Windows agents via SSH (SSH agent plugin) also works fine. But the EC2 plugin still insists on connecting through WinRM (which is a nightmare in itself) or requires the workaround of setting the type to "unix" (with all the implications this may have).
Also, the plugin requires that the SSH key used to connect to the instance is registered in AWS, which is non-sense. It shouldn't matter WHERE a key has been generated, as long as its public part is stored in the authorized_keys file of the connecting user. Please fix these bugs. |
New:
Windows has a native port of OpenSSH since years now. Connecting to static Windows agents via SSH (SSH agent plugin) also works fine. But the EC2 plugin still insists on connecting through WinRM (which is a nightmare in itself) or requires the workaround of setting the type to "unix" (with all the implications this may have).
Please fix this bug. |