Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Warning |
---|
Stopping and restarting the instance after adding a second network interface will release any automatically assigned public IP address. Additionally, adding a second network interface to a non-Amazon Linux EC2 instance causes traffic flow issues. This occurs when there is only one routing table containing one default gateway and traffic that arrives at the second network interface leaves the instance using the first network interface or vice-versa. This is blocked by AWS because a mismatch between MAC address and IP address. To make the second interface work, perform the following steps:
Refer to the AWS documentation and AWS Networking and Charon-SSP for more information. Failure to use the proper steps, may make your instance unreachable! |
...
An Elastic IP address is a persistent, public IPv4 address to be used for one of your network interfaces or instances. You can associate an Elastic IP address with any instance or network interface in your account.
The advantage of associating the Elastic IP address with the network interface instead of directly with the instance is that you can move the network interface with its attributes easily from one instance to another.
The initial automatically assigned public IP address will be removed as soon as you restart the instance after adding a network interface with an Elastic IP address to your instance. Do not restart your instance before you are sure you can reach it via the Elastic IP address. The automatically assigned public IP address will also be disabled if you assign an Elastic IP address to the primary Ethernet interface of the instance.
...