VPC peering
Term VPC1 VPC2
VPC Project1vpc Project2vpc
VPC-ID [Link]./16 [Link]/16
Subnet1 Project1publicsubnet Project2publicsubnet
([Link]/24) ([Link]/24)
Subnet2 Project1privatesubnet Project2privatesubnet
([Link]/24) ([Link]/24)
Route Table Project1-public-rt Project2-public-rt
Internet gateway Internet gatewayproject1 Internet gatewayproject2
VPC peering Steps
1) Create 2 VPC with all detail –RT, IG, Subnet etc.
2) Peering Connection –New Peering –Fill the detail—name—vpc1-vpc2
–vpc , Requester –vpc1, Accepter –vpc2
--same account –same region—ok
3) Select created VPC peering –Action –Accept –ok
4) Route Table –select vpc1 route table—routes—edit routes—add
route– vpc2 IP –target—peering connection---select: vpc1-vpc2 –ok
5) Route Table –select vpc2 route table—routes—edit routes—add
route– vpc1 IP –target—peering connection---select: vpc1-vpc2 –ok
VPC Peering Vs Trasit VPC Vs Trasit Gateway
VPC peering, which offers point-to-point network connectivity between two VPCs.
You can use VPC peering to create a full mesh network that uses individual
connections between all networks. However, this can be very complex to manage
as the number of your VPCs grows. In addition, for every VPC that needs on-
premises connectivity you have to configure an AWS Direct Connect connection or
an AWS Site-to-Site VPN connection. This process could take several weeks of
implementation based on internal business operations, approvals, and
maintenance window schedules.
VPC Peering Vs Trasit VPC Vs Trasit Gateway
Transit VPC solution, which is a way to build a hub-and-spoke topology on Amazon
VPCs, so that they can centralize edge connectivity. Transit VPC allows an easy way
to implement shared services or packet inspection/replication in a VPC. It works
across accounts and is easy to set up through an AWS CloudFormation stack.
However, it leverages instance-based routing that increases costs while lowering
availability and limiting the bandwidth.
VPC Peering Vs Trasit VPC Vs Trasit Gateway
AWS Transit Gateway which offers the same advantages of transit VPC, but it is a
managed service that scales elastically in a highly available product. Transit
gateways are easy to set up and to use, and are designed to be highly scalable and
resilient. By default, you can attach up to 5000 VPCs to each gateway and each
attachment can handle up to 50 Gbits per second of traffic burst. You can also
attach your AWS VPN connections to an AWS Transit Gateway today. With this in
mind, we realized the need for developing an automation tool that would help you
gracefully migrate from your existing transit VPC solution to the AWS Transit
Gateway service.
Trasit Gateway Lab
1) Open VPC --Create 3 VPC in same or different Region
2) Transit gateway -- Transit gateway –create
3) Transit gateway -- Transit gateway Attachments –
4) Route table –edit each vpc route table –
Add route [Link]/8 --target- Transit gateway Attachments ------save
5) Done
VPC Endpoint
• A VPC endpoint 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, VPN connection, or AWS Direct
Connect connection. Instances in your VPC do not require public IP addresses to
communicate with resources in the service. Traffic between your VPC and the
other service does not leave the Amazon network.
• Endpoints are virtual devices. They are horizontally scaled, redundant, and
highly available VPC components. They allow communication between
instances in your VPC and services without imposing availability risks or
bandwidth constraints on your network traffic.
VPC Endpoint Types
Interface endpoints and gateway endpoints
An interface endpoint is an elastic network interface with a private IP address
from the IP address range of your subnet that serves as an entry point for traffic
destined to a supported service. Interface endpoints are powered by AWS
PrivateLink, a technology that enables you to privately access services by using
private IP addresses. AWS PrivateLink restricts all network traffic between your
VPC and services to the Amazon network. You do not need an internet gateway,
a NAT device, or a virtual private gateway.
A gateway endpoint is a gateway that you specify as a target for a route in your
route table for traffic destined to a supported AWS service. The following AWS
services are supported:
• Amazon S3
• DynamoDB
VPC Endpoint Steps
1) Create one VPC with public and private network
2) Launch instances in both subnet
3) VPC—Endpoint—create endpoint –service category—aws resource
–select : [Link]-south-1.s3
--select your new vpc –select private subnet– create endpoint
4) Now connect dbserver through webserver and perform the task of
aws sync (aws cli)
