權限被拒絕（公鑰） ssh ec2 實例 mac

更新2：

$ ls -ld ~/.ssh
drwx------  8 user  staff  272  2 Oct 17:51 /Users/user/.ssh
$ ls -la ~/.ssh/config/file.pem 
-r--------@ 1 user staff 1692 2 Oct 17:11 /Users/user/.ssh/config/file.pem 
$ ls -la file.pem 
-rw-------@ 1 user staff 1692 2 Oct 17:11 localfile.pem

更新：

切換-i和-v標誌後，我現在得到：

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/user/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to ec2-XX-XX-XXX-XXX.areacode.compute.amazonaws.com [IP] port 22.
debug1: Connection established.
debug1: identity file file.pem type -1
debug1: identity file file.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_6.2
debug1: match: OpenSSH_6.2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA fingerprint
debug1: Host 'ec2-XX-XX-XXX-XXX.ap-areacode.compute.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /Users/user/.ssh/known_hosts:11
debug1: ssh_rsa_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: file.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).

我試圖從我的 mac 終端 ssh 到 amazon linux ec2 實例。我按照以下說明操作： http: //docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html

但我明白了Permission denied (publickey)

我的安全設置允許我的公共 ip 訪問 ssh。

它最初成功地實現了：

Permanently added 'ec2-XX-XX-XXX-XXX.areacode.compute.amazonaws.com,YY.YY.YYY.YYY' (RSA) to the list of known hosts.

$ ssh -i ec2vb.pem e2c-user@ec2-XX-XX-XXX-XXX.ap-areacode.compute.amazonaws.com
Permission denied (publickey).

$ ssh -i -v /path/to/ec2/file.pem e2c-user@ec2-XX-XX-XXX-XXX.areacode.compute.amazonaws.com
Warning: Identity file -v not accessible: No such file or directory.
ssh: Could not resolve hostname /Developer/folder/ec2/file.pem: nodename nor servname provided, or not known

我還嘗試更新權限chmod key 600並將我的密鑰複製到使用者.ssh/config文件夾？

debug1: Trying private key: file.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).

您的客戶端將密鑰發送到伺服器，而伺服器不接受它。就您的客戶而言，您的私鑰以及本地文件和目錄權限都很好。您需要從伺服器端對此進行故障排除。我不知道 EC2 伺服器有什麼特別之處，但如果這是一個普通的 Unix 伺服器，你會檢查以下內容：

1. 從 sshd 查找伺服器日誌中的消息。
2. 檢查伺服器上 e2c 使用者的主目錄和 .ssh 目錄的權限。
3. 檢查伺服器上*~ec2-user/.ssh/authorized_keys*文件的權限。
4. 檢查您嘗試使用的此私鑰的公鑰是否實際上位於伺服器上的*authorized_keys中。*這可以通過轉到 EC2 伺服器–>Instances–>（選擇您的實例）–>Description–>Key pair name 來完成（這應該與您正在使用的密鑰的名稱相同）

引用自：https://serverfault.com/questions/632986