【问题标题】:AWS EC2 .pem certificate when creating with Elastic Beanstalk使用 Elastic Beanstalk 创建时的 AWS EC2 .pem 证书
【发布时间】:2013-10-09 12:58:48
【问题描述】:

我已经按照 here 的指导使用 Elastic Beanstalk 设置了新应用程序。
现在我想通过 ssh 访问 EC2 服务器。我没有任何密钥对,所以我生成了新的密钥对,但仍然得到 Permission denied (publickey)。

SSH 跟踪:

$ ssh -v -i ~/.ec2/my.pem ec2-user@ec2-54-215-179-79.us-west-1.compute.amazonaws.com
OpenSSH_5.6p1, OpenSSL 0.9.8y 5 Feb 2013
debug1: Reading configuration data /Users/sergey/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to ec2-54-215-179-79.us-west-1.compute.amazonaws.com [54.215.179.79] port 22.
debug1: Connection established.
debug1: identity file /Users/sergey/.ec2/my.pem type -1
debug1: identity file /Users/sergey/.ec2/my.pem-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
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: Host 'ec2-54-215-179-79.us-west-1.compute.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /Users/sergey/.ssh/known_hosts:26
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: Offering RSA public key: /Users/sergey/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/sergey/.ec2/my.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).

你能帮我解决我做错了什么吗?

【问题讨论】:

标签: ruby-on-rails amazon-web-services ssh amazon-ec2 amazon-elastic-beanstalk


【解决方案1】:

当您使用 beanstalk 时,为什么要 ssh 进入您的 ec2 实例。我建议您更好地创建一个实例并设置环境并部署代码,以便您可以更好地控制您的应用程序和底层操作系统。

【讨论】:

  • 你以前用过beantalk,你有什么建议?我使用它是因为有很好的指南,而且它是谷歌搜索响应中关于在 AWS 上部署 Rails 的第一个结果。
  • 我之前使用过 beanstalk 来制作 ruby​​ on rails stack。如果您正在寻找 ruby​​ 的 PaaS 提供商,我建议使用 heroku 然后 beanstalk。在任何给定的时间点,EC2 都是一个更好的选择,如果它是一个实验项目,尽管它也托管在 EC2 上,但它也托管在 Heroku 上
猜你喜欢
  • 2018-09-20
  • 2015-10-29
  • 2016-09-03
  • 1970-01-01
  • 2016-08-18
  • 2020-08-29
  • 2016-05-12
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多