VPC Peering

5 minutes 5 Questions

VPC Peering enables you to create a network connection between two Amazon Virtual Private Clouds (VPCs) that belong to either the same AWS account or two different accounts. This connection allows instances in both VPCs to communicate with each other as if they were part of the same network. VPC Peering supports both IPv4 and IPv6 communication and is established based on request-acceptance model. Data transferred across VPC peering connection is private and secure, as it does not traverse the public internet. Use cases of VPC Peering include sharing resources across multiple VPCs, reduce the use of VPC host and data transfer costs, and enhance security between VPCs in a multi-account environment.

VPC Peering: A Comprehensive Guide

What is VPC Peering:
VPC Peering is an Amazon Web Service (AWS) feature enabling data exchange between two separate Virtual Private Clouds (VPC). By using Amazon's private network infrastructure, it ensures secured, fast, and efficient communication between two VPCs.

Why is VPC Peering Important:
VPC Peering plays a crucial role in providing cost-effective, low-latency network traffic between VPCs, which can be within the same AWS Region or across different Regions. This can enhance application performance, security and also supports resource sharing across several AWS accounts.

How it Works:
Once a peering connection is established between two VPCs, they function as if they are on the same private network. These VPCs can communicate using private IP addresses, eliminating the need for public IPs, VPN connections, or separate physical hardware.

Exam Tips: Answering Questions on VPC Peering:

Remember that VPC Peering is not transitive. A cannot reach C through B.
VPC Peering can be established between VPCs in different AWS accounts or Regions.
There's no single point of failure for communication or bandwidth bottleneck with VPC Peering.
A maximum of 125 peering connections can be established per VPC.

Using these key points, answering related questions on the exam should be straightforward. You should understand the key features and limitations of VPC Peering and apply these principles to different hypothetical scenarios presented in the exam questions.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

You want to monitor VPC peering connections in your AWS environment to ensure that all peering connections are properly established and configured. Which AWS service should you use?

AWS VPC Flow Logs Amazon S3 Amazon CloudWatch Amazon CloudFront

Correct Answer: AWS VPC Flow Logs

AWS VPC Flow Logs can be used to monitor VPC peering connections and analyze network traffic. Amazon CloudFront is for CDN services, Amazon CloudWatch is for monitoring, Amazon S3 is for object storage, AWS Trusted Advisor is for best practices recommendations, and Amazon Route 53 is for DNS.

Question 2

A company has several VPCs in a hub-and-spoke architecture, and they use VPC peering to connect the VPCs. They want to establish a central VPC as a shared services VPC. What's the best approach to ensure smooth communication between the VPCs?

Use a VPN connection Create nested VPCs Attach an Internet Gateway to each VPC Configure proper route table entries and ensure no overlapping CIDR blocks among the VPCs

Correct Answer: Configure proper route table entries and ensure no overlapping CIDR blocks among the VPCs

For communication between the VPCs, proper route table entries and ensuring no overlapping CIDR blocks are required. VPN connections, Internet Gateways, and NAT gateways are not used in VPC peering. VPC peering can be established between VPCs in different regions, and AWS doesn't support nested VPCs.

Question 3

You've been asked to create a VPC peering connection between two VPCs in separate AWS accounts. What would you do to achieve this?

Create a VPC peering connection and have an owner in one account accept the request from the other account Create a VPC peering connection and use a third-party tool to accept the request Create a VPC peering connection and have AWS automatically accept the request Create separate VPC peering connections in both accounts and merge them

Correct Answer: Create a VPC peering connection and have an owner in one account accept the request from the other account

For VPC peering connections between separate AWS accounts, a VPC owner in one account sends the request, and an owner in the other account accepts the request.

Go Premium