Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fintegrations%2Faws%2Faws-privatelink%2Faws-privatelink-vpc-peering-configuration.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fintegrations%2Faws%2Faws-privatelink%2Faws-privatelink-vpc-peering-configuration.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Note

We highly recommend using the AWS native [Cross-Region Connectivity for PrivateLink](https://docs-docusaurus.kinsta.page/integrations/aws/aws-privatelink/aws-privatelink-cross-region-connection/.md), which provides a significantly easier way to connect across regions without complex VPC peering configurations.

# VPC peering for PrivateLink (legacy)

Use this guide only when native cross-region PrivateLink cannot be used.

This approach is considered legacy and introduces additional operational complexity compared to AWS’s native cross-region connectivity.

[![VPC Peering configuration](/assets/images/vpc_peering-29488bfeac8fbe60cefb15294a15f3fd.webp)](https://docs-docusaurus.kinsta.page/assets/images/vpc_peering-29488bfeac8fbe60cefb15294a15f3fd.webp)

Coralogix PrivateLink requires an Interface VPC endpoint to be created in the AWS region that matches your Coralogix domain. This VPC is referred to as the same-region VPC.

When your monitored workloads (for example, AWS Lambda functions) run in a different AWS region, PrivateLink traffic cannot be routed directly. In this case, VPC peering can be used as a workaround to forward traffic from a cross-region VPC to the same-region VPC that hosts the PrivateLink endpoint.

This tutorial provides step-by-step guidance on configuring your cross-region VPC setup. The configuration ensures that any traffic directed to the PrivateLink domain name follows a route through the VPC peering connection in the same region.

## Prerequisites[​](#prerequisites "Direct link to Prerequisites")

Before proceeding, ensure the following:

* A same-region VPC is already configured with a Coralogix PrivateLink endpoint. Follow the [same-region PrivateLink configuration guide](https://docs-docusaurus.kinsta.page/integrations/aws/aws-privatelink/same-region-connectivity/.md).
* Your Lambda function or workload is deployed in a cross-region VPC.

## VPC Peering configuration[​](#vpc-peering-configuration "Direct link to VPC Peering configuration")

### Step 1: Configure the DNS record[​](#step-1-configure-the-dns-record "Direct link to Step 1: Configure the DNS record")

1. Navigate to **Route 53**, then **Hosted zones**, then **Create hosted zone**.
2. Associate the hosted zone with the cross-region VPC where your Lambda or workload runs.
3. Click **Created hosted zone**.

Note

DNS propagation may take time.

[![Step 1](/assets/images/vpc_step_1-03b0e927a46da6daff699b9744a8cb9f.webp)](https://docs-docusaurus.kinsta.page/assets/images/vpc_step_1-03b0e927a46da6daff699b9744a8cb9f.webp)

### Step 2: Create an alias record for the PrivateLink VPC endpoint[​](#step-2-create-an-alias-record-for-the-privatelink-vpc-endpoint "Direct link to Step 2: Create an alias record for the PrivateLink VPC endpoint")

1. In the private hosted zone, create an **A record**.
2. Set the record name to `ingress.private`.
3. Configure the record as an **alias to a VPC endpoint**.
4. Select the **regional VPC endpoint** in the same-region VPC (do not select AZ-specific endpoints).
5. Save the record.

[![Step 2](/assets/images/vpc_step_2-c26bea3ddc59e6c6acfc4e7f2f6ea43b.webp)](https://docs-docusaurus.kinsta.page/assets/images/vpc_step_2-c26bea3ddc59e6c6acfc4e7f2f6ea43b.webp)

Note

The Route 53 rules may take some time to propagate.

### Step 3: Create the VPC peering connection[​](#step-3-create-the-vpc-peering-connection "Direct link to Step 3: Create the VPC peering connection")

1. Open the **VPC console** in the region of the cross-region VPC.
2. Select **Peering connections**.
3. Choose **Create peering connection**.

### Step 4: Configure the VPC ID (Requester)[​](#step-4-configure-the-vpc-id-requester "Direct link to Step 4: Configure the VPC ID (Requester)")

* In the **local** **VPC to peer with** section, select the region of your same-region VPC.
* Manually enter the VPC ID (Accepter) of the same-region VPC.
* Select **Create peering connection**.

[![Step 4](/assets/images/step_4-529cf40b831f5af4c641efc0e2548a4a.webp)](https://docs-docusaurus.kinsta.page/assets/images/step_4-529cf40b831f5af4c641efc0e2548a4a.webp)

### Step 5: Find and accept the VPC peering request in the target region[​](#step-5-find-and-accept-the-vpc-peering-request-in-the-target-region "Direct link to Step 5: Find and accept the VPC peering request in the target region")

* Switch to the target region.
* In **Peering Connections**, locate and accept the pending peering request.

### Step 6: Update route tables (cross-region VPC)[​](#step-6-update-route-tables-cross-region-vpc "Direct link to Step 6: Update route tables (cross-region VPC)")

* Adjust the routing tables of the cross-region VPC subnets.
* Validate that the routing table(s) in use by the subnets include routes to the same-region VPC CIDR range. The **Target** will be the peering connection you just created.
* Click **Save changes**.

[![Step 6](/assets/images/step_6-fd65fce6be31128888f517515d43ee61.webp)](https://docs-docusaurus.kinsta.page/assets/images/step_6-fd65fce6be31128888f517515d43ee61.webp)

### Step 7: Update routing tables (same-region VPC)[​](#step-7-update-routing-tables-same-region-vpc "Direct link to Step 7: Update routing tables (same-region VPC)")

Repeat the routing configuration for the same-region VPC:

* Add routes back to the cross-region VPC CIDR range
* Use the same VPC peering connection as the target

This ensures return traffic is routed correctly.

Note

* An Internet Gateway or NAT Gateway may be useful for testing and troubleshooting.
* DNS and routing changes may take time to fully propagate.

## Next steps[​](#next-steps "Direct link to Next steps")

After VPC peering and routing are complete, align the VPC configuration with your Lambda function. Instructions can be found [here](https://docs-docusaurus.kinsta.page/integrations/aws/aws-privatelink/aws-privatelink-lambda-configuration/.md).