liveBook · Manning

Network interface

As explained in Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A network interface is a virtual network attachment that provides an instance with network connectivity and associated IP addresses.

A network interface is a virtual network attachment that gives an instance network connectivity and associated private or public IP addresses. An EC2 instance can use multiple interfaces for separate networks, additional addresses, or specialized appliances. section 3.7

Configure an additional interface in the EC2 console:

  • Open EC2, choose Network Interfaces, note the instance’s subnet ID, and select Create Network Interface. section 3.7
  • Provide a description, select the existing subnet and security group, and enable automatic private IPv4 assignment. section 3.7
  • After the interface becomes Available, attach it to the instance, then associate an additional public IP address if required. section 3.7

Separating two web-server networks

An EC2 web server can attach two interfaces in different subnets, such as an application network and a management network. Linux exposes them as interfaces such as eth0 and eth1; HTTP virtual hosts can bind each address to a different document root. section 3.7

Multiple interfaces also support legacy clients that require separate TLS/SSL certificates when SNI cannot be used. Lambda functions can receive interfaces in selected VPC subnets and security groups to reach private resources, but this adds complexity and should be necessary-driven. section 3.7 section 6.2.4

How Amazon Web Services in Action, Third Edition: An in-depth guide to AWS covers it

How deep it goes
Defines the attachment, explains multiple-interface use cases, and gives console steps for creation and attachment without detailing networking internals.
Examples
Uses a two-interface EC2 web server, eth0 and eth1 output, separate virtual hosts, and a Lambda health check for an internal website.
What it assumes
Assumes an EC2 instance, subnet, and security group, while teaching the interface creation, attachment, and address-association sequence.
What you can do after
Operate/configure additional interfaces through the EC2 console and connect Lambda functions to private VPC resources when necessary.
How it connects
Connects EC2, Lambda, VPCs, subnets, security groups, IP addresses, virtual hosts, and TLS/SSL certificates.

Also explained in

Compare how 3 books explain network interface →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Amazon Web Services in Action, Third Edition: An in-depth guide to AWS. The section links point to the parts of the book it draws on.