试图访问的EC2实例时,可能原因超时 [英] Possible reasons for timeout when trying to access EC2 instance

查看:241
本文介绍了试图访问的EC2实例时,可能原因超时的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我不能SSH到我的实例 - 操作超时。可能是什么原因,我能做些什么来解决?一般重新启动需要很长的时间才能生效,而可能只是使事情变得最糟糕

I cannot SSH into my instance - Operation timed out. What could be the reasons why, and what can I do to resolve it? Rebooting normally takes a long time to take effect, and might just makes things worst

更新:这是不是权限 - 我可以正常登录就好了。我怀疑这可能是因为内存问题

UPDATE: It is not about permissions - i can log in normally just fine. I suspect it might be because of memory issues

推荐答案

你的实例设置适当的安全组?即一个允许从网络访问端口22上的实例。 (默认情况下所有的流量是不允许的。)

Did you set an appropriate security group for the instance? I.e. one that allows access from your network to port 22 on the instance. (By default all traffic is disallowed.)

更新:好吧,不是一个安全组的问题。但如果从同一个AMI推出了另一个实例,并且尝试访问该问题仍然存在?也许这个特殊的EC2实例只是随机失败不知何故 - 这是一次这样的事情只发生问题。 (推荐阅读:架构设计的云:最佳实践(PDF),一纸由Jinesh瓦里亚谁是Web服务的布道者亚马逊见特别章节设计故障并没有什么会失败。)

Update: Ok, not a security group issue. But does the problem persist if you launch up another instance from the same AMI and try to access that? Maybe this particular EC2 instance just randomly failed somehow – it is only matter of time that something like that happens. (Recommended reading: Architecting for the Cloud: Best Practices (PDF), a paper by Jinesh Varia who is a web services evangelist at Amazon. See especially the section titled "Design for failure and nothing will fail".)

这篇关于试图访问的EC2实例时,可能原因超时的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆