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

问题描述

我无法通过 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

推荐答案

您是否为实例设置了适当的安全组?IE.一种允许从您的网络访问实例上的端口 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 Varia 撰写的论文，他是 Amazon 的网络服务布道者.请特别参阅标题为为失败而设计，一切都不会失败"的部分.)

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屋！