nywilken
commented
3 years ago Hi @create-atl-delete thanks for reaching out. I will take a look as soon as I can to see if I can reproduce. In the meantime, the SSH connection over session manager uses a local tunnel to proxy the SSH connection over. More specifically, Packer will try to SSH to the localhost:dynamic-port and not directly to the remote instance like you are doing via ssh. Is it possible that this is being blocked.
While the ec2 instance is running what error do you get when you try running
ssh -i <cert_packer_made.pem> Administrator@127.0.0.1:49851?
Note that the port 49851 may not be valid at the next run as Packer will find an available port and use that for the connection. You can see the port in the output of the Packer build.
create-atl-delete
qburst-nikhilsoman
alesiobitaGit
This issue was originally opened by @create-atl-delete in https://github.com/hashicorp/packer/issues/11199 and has been migrated to this repository. The original issue description is below.
Overview of the Issue
I'm attempting to use Packer to build Server 2019 AMIs using the SSH communicator running over Session Manager (SSM). Packer consistently errors out like so:
original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remainIf I keep the Packer instance up after this error, I can connect to it via SSH over SSM from Powershell using
ssh -i <cert_packer_made.pem> Administrator@<instanceid>and providing the password, which I can decrypt using that same certificate in the EC2 console.This proves that:
From my perspective, Packer has everything it needs to properly authenticate and is failing to so. On the Packer instance, I see the following in the event logs:
Reproduction Steps
Try the below build or any build using an Amazon Sever 2019 AMI and SSH over SSM. In my testing, the same issue occurs regardless of VPC/subnet and the particular AMI version.
Packer version
1.74
Simplified Packer Buildfile
Operating system and Environment details
I'm running Packer from a Windows 10 host with:
Log Fragments and crash.log files
2021/08/11 15:05:24 ui: ==> amazon-ebs.stage1: Waiting for SSH to become available... 2021/08/11 15:05:25 ui: amazon-ebs.stage1: Starting session with SessionId: omitted@domain.com-0c14bf492290fc4e6 2021/08/11 15:05:25 ui: amazon-ebs.stage1: Port 8746 opened for sessionId omitted@domain.com-0c14bf492290fc4e6. 2021/08/11 15:05:25 ui: amazon-ebs.stage1: Waiting for connections... 2021/08/11 15:05:25 ui: amazon-ebs.stage1: Connection accepted for session [omitted@domain.com-0c14bf492290fc4e6] 2021/08/11 15:05:25 packer-plugin-amazon_v1.0.0_x5.0_windows_amd64.exe plugin: 2021/08/11 15:05:25 [INFO] Attempting SSH connection to localhost:8746... 2021/08/11 15:05:25 packer-plugin-amazon_v1.0.0_x5.0_windows_amd64.exe plugin: 2021/08/11 15:05:25 [DEBUG] reconnecting to TCP connection for SSH 2021/08/11 15:05:25 packer-plugin-amazon_v1.0.0_x5.0_windows_amd64.exe plugin: 2021/08/11 15:05:25 [DEBUG] handshaking with SSH 2021/08/11 15:05:25 packer-plugin-amazon_v1.0.0_x5.0_windows_amd64.exe plugin: 2021/08/11 15:05:25 [DEBUG] SSH handshake err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain 2021/08/11 15:05:25 packer-plugin-amazon_v1.0.0_x5.0_windows_amd64.exe plugin: 2021/08/11 15:05:25 [DEBUG] Detected authentication error. Increasing handshake attempts. ... above few lines repeat several times ... 2021/08/11 15:06:32 ui error: ==> amazon-ebs.stage1: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain