The more I explore AWS cloud architecture, the more interesting networking becomes. One concept that particularly caught my attention is Amazon VPC Peering and the way it enables private communication between otherwise isolated VPCs.

At first the idea behind VPCs seems simple and one might just say "privately connect 2 VPCs". But as an AWS environment grows, additional peering connections can be established with other VPCs when needed.
Imagine a company where different departments operate their applications in separate VPCs.

For example, the Sales departments has an application running in one VPC, the HR department has its application in another VPC, while the IT Support department provides an internal employee-support application from a third VPC.
Both Sales and HR may need private access to the application provided by IT Support. But instead of exposing the IT Support application to the public internet, separate VPC peering connections can be established.

  • Sales VPC with IT Support VPC and

  • HR VPC with IT support VPC

This simple scenario helped me realize that VPC Peering is not only about connecting networks. It brings together several important AWS networking concepts, including CIDR blocks, route tables, private IP addressing, Security Groups, network isolation, cross-account connectivity, and routing limitations.

So, here is what I found interesting about VPC peering.

What Is VPC Peering?

A VPC peering connection is a networking connection between two Amazon VPCs.

It enables resources in those VPCs to communicate using private IPv4 or IPv6 addresses.

Coming back to our example, we could have:

Sales VPC: 10.0.0.0/16

HR VPC: 10.1.0.0/16

IT Support VPC: 10.2.0.0/16

If Sales and HR both need access to an application hosted by IT Support, we could establish:

Sales VPC ↔ IT Support VPC

and:

HR VPC ↔ IT Support VPC

These are two separate VPC peering connections.

Diagram 1 – Our Example

The three VPCs remain separate environments.

VPC Peering simply creates the required private network paths between them.

There is also an important detail in this diagram:

Sales VPC is not directly peered with HR VPC.

The fact that both are connected to IT Support does not automatically allow Sales and HR to communicate through the IT Support VPC.

We will come back to this later when looking at non-transitive routing.

VPC Peering Is Not Limited to One AWS Account

Another aspect I found interesting is that peered VPCs do not necessarily have to belong to the same AWS account.

For example, imagine that the Sales environment and IT Support environment are operated through separate AWS accounts.

We could have:

AWS Account A → Sales VPC

and:

AWS Account B → IT Support VPC

A VPC peering connection can still be established between them.

Diagram 2 – Cross-Account Peering

This can be useful when an organization separates different workloads or environments into different AWS accounts but still requires controlled private communication between them.

VPCs Can Also Be in Different AWS Regions

The VPCs do not even have to exist in the same AWS Region.

AWS supports inter-Region VPC Peering.

For example:

Sales VPC in eu-west-1

could establish a peering connection with:

IT Support VPC in us-east-1

Diagram 3 – Inter-Region Peering

This can be useful for architectures where workloads in different Regions require private communication.

Possible scenarios include:

  • application-to-application communication;
  • access to shared internal services;
  • cross-account communication;
  • file-sharing networks;
  • data replication for geographic redundancy.

Another thing I found interesting is that VPC Peering is not a traditional VPN connection or customer-managed gateway appliance.

For inter-Region VPC Peering, traffic uses the AWS global backbone rather than traversing the public internet.

For me, this reinforces an important cloud networking idea:

Private communication does not necessarily require making a resource publicly accessible.

How Does VPC Peering Actually Work?

Now let's look at how a VPC peering connection is established.

To keep things simple, let's concentrate on two VPCs from our scenario:

Requester

Sales VPC: 10.0.0.0/16

Accepter

IT Support VPC: 10.2.0.0/16

The Sales VPC will be the requester, while the IT Support VPC will be the accepter.

Several steps are required before their resources can communicate successfully.

Step 1: Send the Peering Request

First, the owner of the requester VPC initiates the peering request.

Conceptually:

Sales VPC → Peering Request → IT Support VPC

Diagram 4 – Peering Request

However, before establishing the connection, there is an important networking requirement.

The CIDR Ranges Must Not Overlap

Our example works because:

Sales VPC: 10.0.0.0/16

IT Support VPC: 10.2.0.0/16

These address spaces do not overlap.

Diagram 5 – Valid CIDRs

Now imagine that both VPCs used:

10.0.0.0/16

Diagram 6 – Invalid CIDRs

If both networks contained the same address space, routing between them would become ambiguous.

This gave me another useful lesson:

Good CIDR planning today can make connecting networks tomorrow much easier.

Step 2: Accept the Peering Request

Once the Sales VPC sends the request, the owner of the IT Support VPC needs to accept it.

Before acceptance, the request is in a Pending Acceptance state.

After acceptance, the VPC peering connection can become Active.

Diagram 7 – Accepting the Request

At first, it can be tempting to think:

The connection is Active, so everything should work now.

But that is not necessarily true.

The VPCs still need to know where to send the traffic.

Step 3: Update the Route Tables

The relevant route tables on both sides must contain routes for the peer VPC.

For the Sales VPC:

Destination Target
10.0.0.0/16 Local
10.2.0.0/16 VPC Peering Connection

The second route essentially tells the Sales VPC:

When traffic is destined for the IT Support network, send it through the peering connection.

The IT Support VPC needs the reverse route:

Destination Target
10.2.0.0/16 Local
10.0.0.0/16 VPC Peering Connection

Diagram 8 – Routing

This was one of my most important takeaways:

Creating network connectivity and configuring routing are two separate steps.

Step 4: Check the Security Groups

Even after establishing the peering connection and configuring the routes, the applications may still be unable to communicate.

Why?

Because the route table answers:

Where should this traffic go?

The Security Group answers:

Should this traffic be allowed?

The Security Groups associated with the resources therefore need to permit the required traffic.

If custom Network ACL rules are being used, those should be checked too.

Diagram 9 – Security Checks

This gives me a useful troubleshooting sequence:

Peering Connection

↓

Route Tables

↓

Security Groups

↓

Network ACLs

↓

Application

An Active peering connection therefore does not necessarily mean that end-to-end communication is working.

Remember Our Sales, HR and IT Support Example?

Earlier, we had this architecture:

Sales VPC ↔ IT Support VPC

and:

HR VPC ↔ IT Support VPC

It might now be tempting to think:

Because Sales can reach IT Support, and HR can reach IT Support, perhaps Sales can also reach HR through IT Support.

This is where one of the most important limitations of VPC Peering appears.

VPC Peering Is Not Transitive

Suppose:

Can Sales use the IT Support VPC as a path to reach HR?

No.

Diagram 10 – No Transitive Routing

VPC Peering does not provide transitive routing.

If the Sales VPC needs direct VPC Peering connectivity with the HR VPC, Sales and HR need their own peering connection:

Sales VPC ↔ HR VPC

Diagram 11 – Direct Connection Required

This also demonstrates why architectures based entirely on VPC Peering can become more difficult to manage as the number of VPCs grows.

For a fully interconnected environment:

  • 3 VPCs → 3 direct connections
  • 4 VPCs → 6 direct connections
  • 5 VPCs → 10 direct connections

This naturally leads to another AWS networking topic worth exploring:

AWS Transit Gateway.

Edge-to-Edge Routing Is Another Limitation

A peer VPC also cannot simply be used as a transit network to reach another network accessible through that VPC.

Imagine the IT Support VPC also has connectivity to another network.

Sales does not automatically inherit that connectivity simply because Sales is peered with IT Support.

Diagram 12 – No Transit

This reinforces a fundamental characteristic of VPC Peering:

VPC Peering provides direct connectivity between peer VPCs. It is not a general-purpose transit mechanism.

What I Learned From VPC Peering

VPC Peering initially looked like a relatively small AWS networking topic.

But studying it helped me connect several concepts together.

My biggest takeaways are:

  • One VPC peering connection connects two VPCs.
  • A VPC can establish multiple separate peering connections.
  • VPCs can belong to the same or different AWS accounts.
  • Inter-Region VPC Peering is possible.
  • Peered VPCs cannot use overlapping CIDR ranges.
  • Creating the peering connection alone is not enough.
  • The relevant route tables must be configured.
  • Security Groups and Network ACLs still matter.
  • VPC Peering is not transitive.
  • A peer VPC cannot simply act as a transit network.
  • Good CIDR planning becomes increasingly important as an AWS environment grows.

Most importantly, exploring VPC Peering reinforced a broader principle that continues to stand out when working with AWS and exploring different cloud architectures:

Understanding how AWS services connect with each other is much more valuable than learning each service in isolation.

VPC Peering isn't only about connecting two VPCs.

It is also about understanding addressing, routing, security, isolation, scalability, and architecture.

And that is what made the topic particularly interesting to me.

Learning becomes even more valuable when knowledge and experiences are shared.
If you have worked with VPC Peering or have a different perspective on the topic, feel free to share your experience in the comments.
There is always something new to learn from one another.

You can also connect with me on LinkedIn www.linkedin.com/in/princeson-okwarauba.

Let’s continue learning, sharing, and building together.