ssh到ubuntu @的aws权限被拒绝（公钥），为什么会失败？

Question

尽管我通常在github或heroku上没有任何问题，但我似乎无法使用SSH连接到AWS。 调试在下面，我尝试过@ubuntu和@ ec2-user（应该是@ubuntu），我也尝试过在Windows上的.ssh中创建配置文件，并添加“ ChallengeResponseAuthentication yes”，似乎将其修复在另一个线程上，但是没有运气。 我已经将.pem文件的权限修改为400。我不明白为什么它说这听起来都是肯定的，但是随后失败了，如果我可以更好地了解错误的原因，我也许能够找到解决方案。 任何帮助非常感谢！

$ ssh -v -i futurebot2.pem ubuntu@ec2-54-218-75-37.us-west-2.compute.amazonaws.com
OpenSSH_6.2p2, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /home/Mark/.ssh/config
debug1: Connecting to ec2-54-218-75-37.us-west-2.compute.amazonaws.com [54.218.75.37] port 22.
debug1: Connection established.
debug1: identity file futurebot2.pem type -1
debug1: identity file futurebot2.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH_5*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA f2:cd:94:4d:a1:9a:b5:67:cb:f7:91:d7:ef:4d:a4:3d
debug1: Host 'ec2-54-218-75-37.us-west-2.compute.amazonaws.com' is known and matches the ECDSA host key.
debug1: Found key in /home/Mark/.ssh/known_hosts:1
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: futurebot2.pem
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

Answer 1

发生这种情况的两个原因。

1. 用户不存在，这可能是由于连接了错误的用户或不是您自己的实例（错误的IP地址）引起的

2. 用户的授权密钥文件中没有您的密钥。 在AWS中，您在启动时选择的密钥已添加到您的实例中，但是如果您想使用其他密钥，则需要将其手动添加到您的authorized_keys文件中。