Page Comparison

...

The following steps are required to create a new network interface that can later be added to an instance:

Step	Details
Locate the Network Interfaces option on the EC2 dashboard and click on it.	Clicking on Network Interfaces opens the list of existing network interfaces.
Create a new interface.	Click on Create Network Interface at the top of the interface list.
Create a new interface.	This opens the interface creation window. On this screen, enter a description, select the subnet the interface should be on (select the subnet to which your instance is to be connected), allow AWS to automatically assign a private IP address or set a custom one from the subnet IP range, and associate the interface with a security group (often the same as for the instance). Click on Create when you are done. The new interface will appear in the overview list. There you can assign a name to the interface. Check that the interface is in state available.

...

Warning

Stopping and restarting the instance after adding a second network interface will release any automatically assigned public IP address. If several interfaces are required where one or more are configured with a public address, use Elastic IP addresses.
Additionally, adding a second IP network interface to a non-Amazon Linux EC2 instance causes traffic flow issues. This occurs in cases of asymmetric routing where traffic to the instance arrives at one network interface and leaves the instance through the other network interface. This is blocked by AWS because a mismatch between MAC address and IP address. Refer to the AWS documentation and the /wiki/spaces/DocCHSSP420CLD/overview (section asymmetric routing considerations) for more information. Failure to use the proper steps, may make your instance unreachable!
If your instance supports enhanced networking there may be naming inconsistencies when adding additional interfaces to a running instance. Please refer to the interface naming section below and the AWS documentation.
The NetworkManager is disabled on Charon-SSP AWS. Therefore, ifcfg-files in /etc/sysconfig/network-scripts are required to define the IP configuration of an interface.

Step	Details
Locate your network interface in the interface list and right-click on it.	The right-click opens the context menu. Select Attach. This will open the window to enter the necessary instance information.
Select your instance and confirm entry.	Select your instance from the drop-down list and click on Attach. The state of your interface will change from available to in-use.
Verify that instance has second interface.	Select your instance in the instance list. The description tab in instance details should now display two network interfaces:

...

The table below describes the steps required to add an Elastic IP address to a network interface.

Step	Details
Locate the Elastic IPs option on the EC2 dashboard and click on it.	This will list the already created Elastic IP addresses.
Allocate a new address.	In the overview list, click on Allocate new address if you need to allocate a new address. It is also possible to assign an existing address to an interface. However, each address can only be used for one instance. This will open the address allocation window.
	In the address allocation window, select the Amazon pool (or your own pool of public addresses), and click on Allocate. The new address will be shown in the list.
Associate the address with the network interface.	Select the address. Then select Actions > Associate Elastic IP address. A window to enter the required options opens. In the window, select to associate the IP address with a network interface, select your network interface from the drop-down menu, connect the public address to the private address of the interface, and click on Associate to complete the step.

...

Versions Compared