VPC
VPC
IP v4 IP v6
32 Bits - 4 Octets 128 Bits - 8 Groups of 4 hexadecimal digits
2 power 32 -- 4.3 Billion IP addr 2 power 128 -- 3400 Trillion Ips
VPC 5 CIDR range -- Adjustable 5 CIDR range -- Quota10.0.0.0/24
CIDR Range -- /16 to /28 /44 to /64 - /4 increments
Address Semanual / Automated - IPAM BYOIP / Amazon Automatic / EIP
Gateway To access internet - IG IG / Egress only IG (Outbound only connecitivity)
EIP Supported Default -- Static IP (EIP)
NAT GW Supported Supported
EC2 Supported for all instance typesSelective Instance Types
Mandatory Optional
analyzer…etc
mal digits
10.0.2.0/24
y connecitivity)
VPC
Subnet
Route Tables
Internet Gateway
CIDR
2 Options
DHCP Options
Virtual Private Cloud - AWS Virtual Network -- Customer dedicated network
Default VPC - AWS Created
Non-Default VPC - Customer Created
A VPC is an isolated portion of the AWS Cloud populated by AWS objects, such as Amazon EC2 instanc
Default VPC - Public ip address auto assign
Public Subnet
Private Subnet
Minimum CIDR - /28
CIDR block size must be between /16 and /28
Routing
Default route -- Local Route (Within AWS VPC) / Internet -- IGW (0.0.0.0/0)
VPC Only
VPC and associated components - NAT GW, Endpoints, …etc
DNS Servers
NTP server
NetBIOS servers
Domain Name
NetBIOS Node Type
Default VPC
Default Subnets
Default Gateway
10.0.0.10
3 periods - dot
n to hosts on a TCP/IP network. The options field of a DHCP message contains configuration parameters.
Connectivity
Bidirectional
vate Gateway - VPN
Outbound) Only Internet Gateway -- IPv6)
10.0.0.0/24
3.108.40.105 192.168.10.16
13.127.139.243
configuration parameters.
.VR@kPYkF-i6kUqwXuP@qF!68uiACt*3
128 64
IP v4 32 Bits 4 Octets
App Tier DB Tier 2 power n IP Addresses CIDR Value
20 Servers 10 Servers 2 power 0 1 /32
30 IPs 20 Ips 2 power 1 2 /31
64 32 2 power 2 4 /30
/26 /27 2 power 3 8 /29
5 Ips 5 Ips 2 power 4 16 /28
59 IP's 27 IP's 2 power 5 32 /27
192.168.10.64 /26 192.168.10.128 /27 2 power 6 64 /26
192.168.10.64 192.168.10.128 2 power 7 128 /25
192.168.10.65 192.168.10.129 2 power 8 256 /24
192.168.10.66 192.168.10.130 2 power 9 512 /23
192.168.10.67 192.168.10.131
192.168.10.68 192.168.10.132
192.168.10.69 192.168.10.133 /16
192.168.10.126 192.168.10.158
192.168.10.127 192.168.10.159
255.255.255.192 255.255.255.224
8bits.8bits.8bits.2bits 8bits.8bits.8bits.3bits
/26 /27
32 16 8 4 2 1
4 x 8 Bits
AWS
65536 IP Addresses
Route Gets automatically created along with VPC creation..
Tables Main
Custom Route tables created by customers for different requirements
Edge Network Virtual Firewall Route table to route the traffic via particular e
Assocation
NAT Gateway or NAT Instance should have to be created in the public subnet -- Elastic IP / P
n check ensures that the instance is the source or destination of all the traffic it sends and receives. Each EC2 in
T feature pre-installed and configured
and receives. Each EC2 instance performs source and destination checks by default
Internet G Enabling traffic for your EC2 instances towards Internet
Bidirectional - Incoming / Outgoing
Ipv4 and I NAT - IPV4 only supported
ances - AWS
vailability risks / constraints
region is chargeable
Interface endpoints and Gateway Load Balancer endpoints are powered by AWS PrivateLink
Interface endpoints are typically accessed using the public or private DNS name associated
Eliminates the need of having a internet gateway / NAT GW / Isntance / VPN connection
Instances doesn’t need a public IP address
Traffic doe Think like a secure channel.. AWS network
Gateway En Gets created and associated at the VPC level Route tables
Interface Endpoints - Interface endpoint -- Sits in the subnet and need to be created for eac
ENI created -- Elastic Network Interface
Security Group integration -- Port, Protocol, Source / destination
Private IP as well private DNS name will get assigned - Private DNS zo
eway Load Balancer endpoints, and Gateway endpoints.
wered by AWS PrivateLink, and use an Elastic Network Interface (ENI) as an entry point for traffic destined to the
ate DNS name associated with the service, while Gateway endpoints and Gateway Load Balancer endpoints serv
oute tables
need to be created for each AZ
Source / destination
assigned - Private DNS zone…
for traffic destined to the service.
d Balancer endpoints serve as a target for a route in your route table for traffic destined for the service.
d for the service.