- Newest
- Most votes
- Most comments
Are you sure you want to continue connecting (yes/no/[fingerprint])?
From the output above it loks like you replied no to this, and so the connection terminates.
What happens when you answer yes?
Which version of Linux is installed on the EC2?
This hints at it being Debian OpenSSH_8.4p1 Debian-5+deb11u2
and the default user for Debian is admin not ec2-user https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-users.html#ami-default-user-names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'ec2-3-80-22-124.compute-1.amazonaws.com,3.80.22.124' (ECDSA) to the list of known hosts. debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory debug1: Will attempt key: WebKey.pem explicit debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: WebKey.pem debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. ec2-user@ec2-3-80-22-124.compute-1.amazonaws.com: Permission denied (publickey).
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 19 days ago
- AWS OFFICIALUpdated a year ago
I tried all the different user names (admin, ec2-user, ec2_user, root, ubuntu ....). I think the issue is at the server side. Don't know if this matters: read_passphrase: can't open /dev/tty: No such file or directory