Open MarkoPaul0 opened 3 years ago
Simillar issue. The same process that works on one instance does not work on another. After pushing key and trying to connect it ends with Permission denied (publickey)
Haven't been able to figure this one out
This is still an issue for me. I would really appreciate any help :)
I'm stuck in this too. At the server side I see these logs
Jul 25 22:47:17 xxxxxxxxxxx sshd[5498]: AuthorizedKeysCommand /usr/share/ec2-instance-connect/eic_run_authorized_keys ubuntu SHA256:xxxxxxxxxxxxx failed, status 124
Jul 25 22:47:17 xxxxxxxxxxx sshd[5498]: Connection closed by authenticating user xxx xx.xx.xx.xx port 33464 [preauth]
Also same issue here:
EC2InstanceConnect - DEBUG - Successfully pushed the public key to i-XXXXXXXXXXXXXXXXX EC2InstanceConnect - DEBUG - Generated command: ssh -o "IdentitiesOnly=yes" -i /var/folders/x9/qblbrv210894j9448_nkzf900000gn/T/tmpdhvvdwwb ubuntu@XXX.XXX.XXX.XXX ubuntu@XXX.XXX.XXX.XXX: Permission denied (publickey).
EC2InstanceConnect - DEBUG - Deleting the private key file: /var/folders/x9/qblbrv210894j9448_nkzf900000gn/T/tmpdhvvdwwb
I have the same issue
same issue
When running the following command on mac os:
I get the following output
You can see the final lines suggest the temporary key was successfully pushed, yet get permission denied after that. The time sync solution reported by others did not solve my problem. This is rather strange since I am able to mssh into other instances, all of which are Amazon Linux 2. I am doing all of this from a mac. Any help would be really appreciated :)