为什么我无法访问位于公有子网中的 EC2 实例,即使它具有公有 IPv4 地址?
我正在 Amazon EC2 中迈出第一步,因此我在公共子网中创建了一个 EC2 实例(我实际上致力于获取基本的背景知识)。
我可以通过 RDP 访问该实例,但我无法通过其公共 IPv4 地址访问该实例(由于超时而导致连接终止)。
如果我 ping IPv4 地址,我会收到消息: 已发送 4 个包裹 收到 0 个包裹 4个包裹丢失 100% 丢失
也许有任何明显的原因(安全组配置错误?)
VPC 配置:
实例 - 配置,包括安全组:
<一href="https://i.sstatic.net/zJYUe.png" rel="nofollow noreferrer">
一些详细信息:
- 该实例被放置在公共子网中。
- “自动分配公共 ipv4 地址”选项设置为 在子网内“启用”。在首次启动之前,也为实例选择了此选项
- 该实例具有公共 IPv4 地址和公共 IPv4-DNS(因此 EIP 不是必需的?)
- 路由
- 公共子网的路由表具有到 Internet 网关网络 ACL 的 双向完全开放
- 端口 80、443、8443 对目标 0.0.0.0/0、端口 22 和 0.0.0.0/0 开放。 3389 仅针对自己的 IPv4(传入数据)
- 传出数据流量也完全开放(目标 0.0.0.0/0)
我的安全组配置是否过于严格/错误?也许是防火墙问题? 感谢您的帮助!
I am doing my first steps in Amazon EC2 and therefore i created an EC2 instance in a public subnet (i actually work on getting the essentiell background knowledge).
I am able to access the instance via RDP, but i am not able to access the instance via it´s public IPv4 address (connection termination due to timeout).
If i ping the IPv4 address i got the message:
4 packages sent
0 packages received
4 packages lost
100% loss
Maybe there is any obvious reason (misconfiguration in security group?)
VPC configuration:
Instance - configuration, including security-group:
Some detailed information:
- The instance was placed in a public subnet.
- The option "assign public ipv4 address automatically" was set to
"enabled" inside the subnet. This options was also chosen for the instance prior to first start - The instance has a public IPv4 address and a public IPv4-DNS (so EIP shouldn´t be necessary?)
- The routing table of the public subnet has a route to internet gateway
- network ACL is fully opened in both directions
- ports 80, 443, 8443 are open for target 0.0.0.0/0, ports 22 & 3389 only for own IPv4 (incoming data)
- outgoing data traffic is also completely open (target 0.0.0.0/0)
Are my security groups configured too restrictively /wrong? Maybe a firewall issue?
Thank you for your help!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论