Scribd
Upload
16 views

Amazon VPC Peering

2

Uploaded by

mirzakhajamoinuddinnawaz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
16 views

Amazon VPC Peering

2

Uploaded by

mirzakhajamoinuddinnawaz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

What is Amazon VPC Peering?

• Secure and Private Network Communication


Between VPCs
• Direct Communication: The VPCs can be in
the same or different AWS regions (Inter-
Region VPC Peering).
• Private Connectivity: Traffic between VPCs
stays within the AWS network and does not go
over the public internet.
How VPC Peering Works
• Request and Accept Process:
– VPC Peering Request: The owner of one VPC sends a peering
request to the other VPC.
– Acceptance: The owner of the other VPC accepts the request,
establishing the connection.
• Routing: Once peered, you update the route tables in
both VPCs to allow traffic to flow between them.
• No Overlapping CIDR Blocks: VPC Peering requires that
the VPCs involved do not have overlapping CIDR blocks.
• No Transitive Peering: Traffic cannot pass from one VPC
to another via a third peered VPC.
VPC Peering Limitations
• No Transitive Peering: If VPC A is peered with VPC B, and
VPC B is peered with VPC C, traffic between VPC A and VPC
C is not allowed.
• No Edge-to-Edge Routing: You cannot use a VPC peering
connection to connect to an AWS service (like a VPN or
Direct Connect) in a peered VPC.
• Bandwidth Limits: The bandwidth of a VPC peering
connection is the same as the network bandwidth
between instances (based on instance types).
• Security Groups: You need to manually update security
group rules to allow traffic between peered VPCs.
Setting Up VPC Peering
• Step 1: Create Peering ConnectionInitiate a VPC
Peering request between two VPCs in the AWS
Management Console or using AWS CLI.
• Step 2: Accept Peering RequestThe owner of the other
VPC accepts the peering request.
• Step 3: Update Route TablesAdd routes to the route
tables of both VPCs to enable traffic between the VPCs.
• Step 4: Configure Security GroupsUpdate security
group rules to allow traffic from the peered VPC's CIDR
block.
Use Cases for VPC Peering
• Cross-Account Communication:
– Peering VPCs owned by different AWS accounts to allow secure
data exchange without needing VPNs.
• Multi-Region Applications:
– Use VPC Peering to build applications that span across AWS
regions, ensuring low-latency communication.
• Microservices Architecture:
– Separate services into different VPCs and use peering to allow
communication between the services.
• Shared Services:
– Share resources like databases or monitoring tools across different
VPCs within an organization using peering.
Benefits of VPC Peering
• Scalability: Seamlessly connect VPCs to facilitate
resource sharing (e.g., databases, microservices).
• Cost-Effective: No need for VPN connections, internet
gateways, or AWS Direct Connect for communication
between peered VPCs.
• Secure Communication: The communication between
VPCs happens over AWS's private network infrastructure.
• Cross-Region Peering: You can create a peering
connection between VPCs in different regions to allow
for cross-region data access.
Cost Considerations
• Data Transfer Costs: Traffic between VPCs in
the same region is free. Inter-region VPC
Peering incurs data transfer charges.
• Bandwidth Costs: Data transfer charges apply
based on the volume of traffic between
peered VPCs.
• No Gateway Required: Unlike VPN or Direct
Connect, VPC Peering doesn’t require
additional infrastructure costs like gateways.

You might also like