---
title: "How to Do Peering between VPCs in Different Regions for AWS"
slug: "how-to-peer-vpcs-diff-regions-aws"
updated: 2025-12-23T14:50:09Z
published: 2025-12-23T14:50:09Z
canonical: "docs.swxtch.io/how-to-peer-vpcs-diff-regions-aws"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.swxtch.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Peer between VPCs in Different Regions for AWS

**WHAT TO EXPECT**

In order to successfully do Peering Connections between VPCs on AWS, a user must configure their route tables to allow traffic between them. This will ensure that packets destined for a specific network segment in the other VPC are correctly routed. The VPCs can be located in different regions.

  
  

**In this article**, users will learn how to create a peering connection between different regions, modify the route tables, and edit the subnet Associations.

### STEP ONE: Create a Peering Connection between Different Regions

1. **Go** to the **VPC Dashboard** and select **Peering Connections**.
2. **Click** on **Create peering connection**.

![AWS-Peering_Create-Peering-Connections](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_Create-Peering-Connections.png)
3. **Edit** the following in the **Create peering connection**form:
  1. **Set** a descriptive name. In the example, the user lists the connection between VPCs from Oregon and N. Virginia.
  2. **Select** the VPC of the instance you want to connect from.
  3. **(Optional, if the target VPC is in another region) Select** **Another Region** and select the destination region from the dropdown menu.
  4. **Enter** the **VPC ID** of the target VPC in the target region.
  5. **Add** any tag needed for organizational purposes.

![AWS-Peering_create-peering-form](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_create-peering-form.png)
4. **Click** the **Create peering connection** button. A new Peering Connection should now be listed for the region you're in.

![AWS-Peering_create-peering-complete](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_create-peering-complete.png)

> [!NOTE]
> **PLEASE NOTE**
> 
> A "mirrored connection" will be created on the "destination" region. It must be accepted manually to be active.
5. **(Optional, if the target VPC is in another region) Change** to the other region.
6. **Go** to **Peering Connections**.
7. **Select** the new **Peering Connection** listed as "*Pending acceptance*."

![AWS-Peering_peering-request](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_peering-request.png)
8. Under the Actions dropdown, select **Accept request**.

![AWS-Peering_accept-request](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_accept-request.png)

### STEP TWO: Modify Route Tables in Both Regions

Once the peering connections are created, the route table must be modified in both regions. Start with the 1st region and complete STEP TWO and STEP THREE.

1. **Go** to the **VPC Dashboard**.
2. **Click** on **Route tables** in the “Virtual private cloud” section.
3. **Click** the **Create route table** button.

![AWS-Peering_route-tables](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_route-tables.png)
4. **Edit** the following in the **Create route table**form:
  1. **Enter** a descriptive name.
  2. **Select** the correct VPC.
  3. **Add** any necessary tags.

![AWS-Peering_route-tables-form](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_route-tables-form.png)
5. **Click** the **Create route table** button.
6. **Select** the **Route table ID** of the route table you just created.

![AWS-Peering_route-table-id](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_route-table-id.png)
7. **Click** the **Edit routes** button on the next screen.

![AWS-Peering_edit-routes](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_edit-routes.png)
8. **Add** the **Destination** by entering the CIDR of the destination network.
9. Under Target, **select** the recently created **Peering Connection** from the list.

![AWS-Peering_edit-routes-form](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_edit-routes-form.png)
10. **Click** the **Save changes** button.

**PLEASE NOTE**

If you need the agents to have access to the internet, you will also need to add the route for the 0.0.0.0/0 towards the NAT gateway.

### STEP THREE: Edit Subnet Associations

1. **Go** to **Subnet associations** tab.
2. **Click** the **Edit subnet associations** button under the **Explicit subnet associations** box.

![AWS-Peering_edit-subnet-associations](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_edit-subnet-associations.png)
3. **Select** the subnet(s) of the instance that must be connected to the destination.

![AWS-Peering_edit-subnet-associations-form](https://cdn.document360.io/84c5db44-f675-4f33-a980-5d3fc63073ca/Images/Documentation/AWS-Peering_edit-subnet-associations-form.png)
4. **Click** the **Save associations** button.

**PLEASE NOTE**

It is important that security groups on each Subnet on both Regions match and should both encompass the port exceptions listed in the [cloudSwXtch System Requirements](/v2/docs/cloudswxtch-prerequisites)article.
5. **Repeat** STEP TWO and THREE for the Other Region