简体繁体 English

AWS Elastic IP无法发送流量

[英]AWS Elastic IP Unable to Send Traffic

原文 2015-08-14 16:21:40 9 1 amazon-web-services/ amazon-ec2

I have an EC2 instance that had a dynamic public IP. 我有一个具有动态公共IP的EC2实例。 Due to changing requirements I assigned a new Elastic IP. 由于需求的变化，我分配了一个新的Elastic IP。 I shut down the instance and restarted it. 我关闭实例并重新启动它。 The console now shows the new IP and no longer the old, dynamic one. 现在，控制台显示新IP，不再显示旧的动态IP。

Problem is now I can not ping nor curl/wget to the public Internet any longer from this instance. 现在的问题是，我无法再从该实例ping或卷曲/获取公共互联网。 I do have an outgoing rule for port 80 and 443 setup. 我确实有端口80和443设置的传出规则。 I also allow ICMP in both directions. 我也允许双向ICMP。

I have a load balancer setup in another instance. 我在另一个实例中有一个负载平衡器设置。 That instance can access the problematic instance over the private IP no problem. 该实例可以通过专用IP访问有问题的实例。

I did notice that while all my other instances list their public IP (dynamic or Elastic) the instance in question lists "ec2-xxxx.compute-1.amazonaws.com". 我确实注意到，虽然我所有其他实例都列出了其公共IP（动态或弹性），但有问题的实例列出了“ ec2-xxxx.compute-1.amazonaws.com”。 Not sure what to make of that... 不知道该怎么做...

What could be my issue? 可能是我的问题？

1 个解决方案

If you are not seeing the public IP show up in the console for the system, but instead are seeing the hostname as you mention, it means that your public IP is NOT assigned to the instance. 如果您没有看到公共IP在系统的控制台中显示，而是看到了您提到的主机名，则意味着您的公共IP没有分配给实例。 Suggest you go to the Elastic IPs section of the console and re-attach the EIP to the instance. 建议您转到控制台的“弹性IP”部分，然后将EIP重新连接到实例。

Note, if you are not running in a VPC, when you reboot the instance, the EIP will drop off the instance. 请注意，如果您不在VPC中运行，则在重新启动实例时，EIP将退出该实例。