To utilize our Coralogix AWS PrivateLink feature, it is essential to establish a VPC endpoint within the Coralogix AWS region corresponding to your Coralogix domain—commonly referred to as a same-region VPC.
In cases where your AWS resources for monitoring are located in a different region, you can achieve the required connectivity by employing VPC peering. This involves deploying your Lambda in a cross-region VPC, strategically positioned in proximity to the source.
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, ultimately reaching the PrivateLink endpoint.
When your Lambda is being deployed into a cross-region VPC, use VPC peering to allow the Lambda local VPC to communicate over the PrivateLink through the same-region VPC. To do this, configure the same-region VPC.
STEP 1. Configure the DNS record to give it time to propagate.
STEP 2. Configure an A record type pointing to the PrivateLink VPC endpoint.
ingress.private
, with an alias to VPC endpoint – that is, an alias pointing to the VPC PrivateLink endpoint of your same-region VPC. Notes:
STEP 3. Set up the VPC peering connection between the two VPCs.
STEP 4. Set the VPC ID (Requester) to the cross-region VPC that will host your Lambda.
STEP 5. Find and accept the VPC peering request in the target region.
STEP 6. Adjust your routing tables.
STEP 7. Once you’ve added the route to all of your subnets, do the same for the same-region VPC. This ensures return traffic can be routed back to the cross-region VPC.
Notes:
Align the VPC to your Lambda. Instructions can be found here.
Need help?
Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.
Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].