2012-04-30 187 views
2

我試圖使用SSH訪問EC2上的新Ubuntu實例。我注意到很多人都遇到了同樣的問題,並使用了不同的解決方法,但迄今爲止還沒有能夠實現這一目標。對AWS EC2的SSH訪問權限 - 拒絕權限

任何幫助將不勝感激。

>$ ssh -l ubuntu -v -i TBKEY1.pem ec2-46-137-225-40.ap-southeast-1.compute.amazonaws.com 
>OpenSSH_6.0p1, OpenSSL 1.0.1b 26 Apr 2012 
>debug1: Connecting to ec2-46-137-225-40.ap-southeast-1.compute.amazonaws.com [46.137.225.40] port 22. 
>debug1: Connection established. 
>debug1: identity file TBKEY1.pem type -1 
>debug1: identity file TBKEY1.pem-cert type -1 [-pebug1: Remote protocol version 2.0, remote software version OpenSSH_5.3p1 Debian-3ubuntu6 
>debug1: match: OpenSSH_5.3p1 Debian-3ubuntu6 pat OpenSSH_5* 
>debug1: Enabling compatibility mode for protocol 2.0 
>debug1: Local version string SSH-2.0-OpenSSH_6.0 
>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: 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 77:49:93:95:2f:c5:b2:9c:d3:1b:f0:34:fb:23:b1:8c 
>debug1: Host 'ec2-46-137-225-40.ap-southeast-1.compute.amazonaws.com' is known and matches the RSA host key. 
>debug1: Found key in /home/Ma/.ssh/known_hosts:1  
>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: TBKEY1.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). 

回答

1

一旦我有類似的問題。我無法解決它,但我解決了它。你可以做的是從你嘗試訪問的機器的EBS中創建一個AMI,然後從這個AMI中啓動一個新的實例並指定創建一個新的密鑰對。然後,AWS應該將您的新私鑰添加到allowed_keys中,並讓您進入新機器。那時你可以擊落舊的。

希望這會有所幫助。

0

因爲你是從服務器獲取Permission denied (publickey)消息存在連接任何問題。 確保與TBKEY1.pem相關的密鑰對與您的實例相關聯。如果它被鏈接,那麼它應該顯示爲下面的截圖。

enter image description here

你可以找到更多的細節here