Networking in Public Clouds

This section defines typical cloud services, from SaaS to IaaS, provides an overview of network-related IaaS services, and describes typical multi-tenant requirements.

Watch this part of the module if you decided to use AWS for your hands-on projects.

Virtual Private Cloud (VPC) service is the foundation of AWS networking. This section describes VPC concepts, subnets within VPCs, and VPC/subnet addressing.

Subnets are useless without servers connected to them. In this section we'll focus on AWS implementation of VM network interfaces, network interface addressing, and supporting services like DNS and DHCP.

The section also covers advanced concepts like public and private IP addresses, elastic IP addresses, and elastic network interfaces.

VPC Route Tables are almost like VRFs with a few significant differences:

• Route tables are applied to subnets;
• All route tables share the entry for local VPC CIDR block.

This section describes the route tables and details of packet forwarding within VPC.

VPC Internet connectivity is usually provided through an Internet gateway. IPv6 hosts that don't provide services to outside clients can use egress-only gateway; similar IPv4 hosts can access Internet through NAT gateway or NAT instance.

This section describes all three mechanisms, and the adjustments to route tables that have to be made to support them.

Watch this part of the module if you decided to use Azure for your hands-on projects.

In this section you'll learn about Azure virtual networks and subnets, VM interfaces, private and public IP addresses, and DNS and DHCP services.

Each subnet in Azure Virtual Network can have a custom route table. This section describes:

• System (default) routes always present in virtual networks;
• Route import from BGP sessions between VNG and customer routers;
• User-defined static routes.

The examples cover a range of scenarios, from simple private subnet with no Internet access to complex service insertion.

Internet access is built into Azure VNet service, and a default route is part of the default routing table. This short section explains the remaining NAT intricacies.

While most public clouds base their container networking on Kubernettes, the basic limitations of running networking stacks in Linux namespaces still apply, and you will get a thorough overview of those limitations in this webinar.

Access content

In this assignment you'll create a full-blown virtual networking infrastructure (virtual network, subnets, Internet access, route tables) and deploy a web server, a back-end server, and a jump host.