> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-services/virtual-private-cloud-vpc-peering.md).
# Virtual Private Cloud (VPC) Peering
Establish communication between GCP VPCs via VPC peering
Virtual Private Cloud (VPC) peering establishes a direct networking connection between two VPCs, allowing traffic to flow seamlessly between them. With VPC peering, resources in the connected VPCs can communicate as though they are part of the same network, even if the VPCs reside in different regions (referred to as Inter-Region VPC peering).
This connection is ideal for facilitating data transfer between environments. For instance, if you manage multiple GCP projects, you can peer the VPCs across those projects to enable secure communication and resource sharing, such as setting up a file-sharing network.
## Setting Up VPC Peering in DuploCloud
To set up VPC peering in DuploCloud, first configure peering in the source Infrastructure, then confirm peering in the destination Infrastructure.
### Configure peering in the source Infrastructure
1. In the DuploCloud Portal, navigate to **Administrator** -> **Infrastructure**.
2. In the **NAME** column, select the name of the source Infrastructure.
3. Select the **Peering** tab.
4. Click **Add**. The **Create VPC Peering** pane displays.
The Create VPC Peering pane
5. Select the **Destination Infrastructure**.
6. Optionally, enable **Bi-Direction/Duplex Peering**, **Export Custom Routes**, **Import Custom Routes**, **Export Subnets Routes With Public IP**, or **Import Subnet Routes With Public IP**. Complete additional fields/selections as required.
7. Click **Create**. VPC peering is configured.
### Confirm peering in the destination Infrastructure
1. In the DuploCloud Portal, navigate to **Administrator** -> **Infrastructure**.
2. In the **NAME** column, select the name of the destination Infrastructure.
3. Select the **Peering** tab.
4. In the row of the peering connection, click the menu icon ().
5. Select **Edit**. The **Update VPC Peering** pane displays.
6. Click **Update**. Verify that the peering status is **Active**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.duplocloud.com/docs/automation-platform/overview-1/gcp-services/virtual-private-cloud-vpc-peering.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=b79a90d6-3da8-48da-b182-ed50730b2dfe)
).
5. Select **Edit**. The **Update VPC Peering** pane displays.
6. Click **Update**. Verify that the peering status is **Active**.
