VPC – Scriptorium

[AWS Lab] VPC – Public Subnet

In this lab, we will learn how to create a public subnet and test it with an EC2 instance.

Overview

VPC
- Create a VPC and a public subnet
EC2
- Create an EC2 instance inside the public subnet
- Setup the website in the EC2 instance using “httpd“
- Access the website via the public IP address of the EC2 instance

[AWS] VPC – NAT Gateway

NAT (Network Address Translation)

NAT remaps source IPs or destination IPs. (It translates private IPs to public IPs and vice versa.)

Static NAT
- A private IP is mapped to a public IP at a 1:1 ratio. (such as Internet Gateway).
Dynamic NAT
- A range of private IPs are dynamically mapped to one or more public IPs (Home router or NAT Gateways).
- To achieve high availably, create one dynamic NAT per AZ.

[AWS] Transit Gateway

AWS Transit Gateway is used to simplify your AWS network architecture (topology) by allowing to have transitive peering between hundreds and thousands of VPCs and on-premise data centers.

[AWS] VPC Endpoints

A VPC Endpoint is a gateway object within a VPC and can be used to connect privately to AWS public services or other VPC endpoints without the need for Internet Gateway or a public subnet.

[AWS] VPC Peering

VPC Peering allows direct communication between VPCs (inter-region & cross-account) using OSI Layer 3 (Network). Once the VPCs are connected, 2 VPCs can communicate using private IP addresses.

[AWS] VPC – VPC Flow Logs

This post deals with how to monitor VPC traffics. VPC Flow Logs can capture IP traffic information going from or to the network interfaces in a VPC.

[AWS] VPC – Security

VPCs can be protected with 2 layers of firewalls; One for a subnet (NACL) and another for an instance (Security Group).

[AWS] VPC – IGW

Internet Gateway (IGW) is a VPC component that allows communication between resources in the VPC and the internet. It is horizontally scaled, redundant, and highly available.