Learning AWS Day by Day — Day 22 — VPC Peering and Endpoints

Learning AWS Day by Day — Day 22 — VPC Peering and Endpoints

Exploring AWS !!

Day 22:

VPC Peering and VPC Endpoints

VPC Peering:

Network connection between 2 VPCs which enables traffic flow between them using IP addresses.

Peering connection can be created between VPCs in same or different accounts and between VPCs in same or different region.

Scenarios:

2 VPCs (with same network) peered with 2 subnets in same VPC.

2 VPCs peered with specific subnets.

1 VPC peered with 2 VPCs using longest prefix match.

VPC Endpoints:

A VPC enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by AWS Privatelink without requiring an internet gateway, NAT device, VPC connection or AWS Direct Connect connection.

So, VPC Peering can be avoided.

Gateway Endpoint: can be used to connect to AWS services and is located outside subnet..

Interface Endpoint: located inside subnet of VPC, it uses Privatelink where route tables aren’t required.