Dear Team,
I’m using AWS Marketplace Image (ami) as my source ami in packer build script.
Getting ssh authentication error while provisioning phase in packer. Tried with ssh_password, without any ssh_password and ssh_private_key_file option on packer build script.
But nothing seems working. Could someone guide me what is the correct communicator credential to be used for connecting to the packer created instance?
Please find the error log for your reference.
2020/11/06 15:38:55 packer-builder-amazon-ebs plugin: [INFO] Attempting SSH connection to 52.66.170.64:22…
2020/11/06 15:38:55 packer-builder-amazon-ebs plugin: [DEBUG] reconnecting to TCP connection for SSH
2020/11/06 15:38:55 packer-builder-amazon-ebs plugin: [DEBUG] handshaking with SSH
2020/11/06 15:38:55 packer-builder-amazon-ebs plugin: [DEBUG] SSH handshake err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2020/11/06 15:38:55 packer-builder-amazon-ebs plugin: [DEBUG] Detected authentication error. Increasing handshake attempts.
==> amazon-ebs: 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
==> amazon-ebs: Terminating the source AWS instance…
==> amazon-ebs: Cleaning up any extra volumes…
==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Deleting temporary security group…
==> amazon-ebs: Deleting temporary keypair…
2020/11/06 15:39:30 [INFO] (telemetry) ending amazon-ebs
2020/11/06 15:39:30 machine readable: error-count string{“1”}
==> Some builds didn’t complete successfully and had errors:
2020/11/06 15:39:30 machine readable: amazon-ebs,error string{“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”}
==> Builds finished but no artifacts were created.
2020/11/06 15:39:30 Cancelling builder after context cancellation context canceled
Build ‘amazon-ebs’ errored: 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
==> Some builds didn’t complete successfully and had errors:
–> amazon-ebs: 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
==> Builds finished but no artifacts were created.
Regards,
Guru Mohan G