新的EC2实例腻子连接被拒绝 [英] Connection refused on new EC2 Instance putty

问题描述

我已经根据现有服务器生成的AMI在EC2上创建了服务器实例。在创建过程中一切正常，我为新服务器指定了与旧服务器相同的密钥。但是，当我尝试通过腻子连接到新服务器时，收到连接被拒绝消息。另外，尽管我选择了允许ICMP的默认组，但我无法ping通到公共地址。服务器状态为正在运行。有什么想法我无法联系吗？

请注意，nmap探针会提供以下输出：

  PORT STATE服务
 22 / tcp关闭ssh 
 80 / tcp关闭http 
 2144 / tcp关闭未知
 10000 / tcp关闭snet-sensor-mgmt 
  

我很确定这意味着ssh没有运行，尽管端口是打开的。知道为什么它将在运行AMI的系统上运行，而不是在生成AMI的系统上运行吗？难道所有相同的服务都不应该开始吗？

解决方案

这确实是一个安全组/权限问题。默认安全组看起来是打开的，但实际上实际上关闭了所有信息，

https://serverfault.com/questions/245916/why-cant-i-ssh-or-ping-my- brand-new-amazon-ec2-instance

I've created an instance of a server on EC2 based on an AMI generated from an existing server. All goes well during the create, and I specify the same key for the new server as the old. However, when I try to connect to the new server via putty, I get a "connection refused" message. Also, I'm unable to ping to the public address, although I selected the "default" group which allows ICMP. The server status is "running". Any ideas why I can't connect?

Note that an nmap probe gives this output:

PORT      STATE  SERVICE
22/tcp    closed ssh
80/tcp    closed http
2144/tcp  closed unknown
10000/tcp closed snet-sensor-mgmt

I'm pretty sure this means that ssh isn't running, although the port is open. Any idea why it would be running on the system I did the AMI from, but not on the one the AMI was generated from? Shouldn't all the same services be starting?

解决方案

It did turn out to be a security group/permissions issue. The default security group looks open, but actually shuts everything down, per this post:

https://serverfault.com/questions/245916/why-cant-i-ssh-or-ping-my-brand-new-amazon-ec2-instance

这篇关于新的EC2实例腻子连接被拒绝的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！