Our next-gen architecture is built to help you make sense of your ever-growing data Watch a 4-min demo video!
Formats: PNG, PDF, and SVG
Files size: 2.8 MB
For brand guidelines, please click here
AWS PrivateLink provides private connectivity between virtual private clouds (VPCs), supported AWS services, and your on-premises networks without exposing your traffic to the public internet. Interface VPC endpoints, powered by PrivateLink, connect you to services hosted by Coralogix.
Integrate with the PrivateLink endpoint to:
This tutorial provides AWS Coralogix PrivateLink endpoints, as well as instructions for standard and cross-region configuration.
Coralogix exposes the AWS PrivateLink endpoint in all Coralogix AWS regions.
|Coralogix Domain||Coralogix AWS Region||Service Name||OpenTelemetry –|
In order to configure PrivateLink successfully and connect to services hosted by Coralogix, it is required that you create a VPC endpoint in the Coralogix AWS region matching your Coralogix domain.
Instructions on how to configure cross-region VPC interface endpoints for AWS services can be found below.
STEP 1. Create a VPC endpoint.
STEP 2. Name the VPC endpoint and select the service category: PrivateLink Ready partner services.
STEP 3. Input the Service name associated with your Coralogix AWS region, as per the above table.
STEP 4. Click Verify service.
STEP 5. Select a VPC in which to create the endpoint.
STEP 6. Expand the Additional settings section and Enable DNS name.
STEP 7. Select a security group to enable traffic to this VPC endpoint.
STEP 8. Click Create endpoint.
STEP 9. Verify your configuration.
STEP 10. Enter the connected VPC and type the following command, adjusted per region:
#example US region #telnet ingress.private.coralogix.us telnet <ingress.private.<region> 443
This section demonstrates how to configure cross-region Amazon VPC endpoints to access AWS resources using PrivateLink.
STEP 1. Implement the standard configuration (STEPS 1 – 10) above.
STEP 2. Set up VPC peering between the Source VPC and Destination VPC.
STEP 3. Navigate to the Destination VPC Endpoint page and copy the first DNS from the list of DNS names.
STEP 4. Make a private DNS entry, converting the DNS name to the Coralogix endpoint in the region.
Here is an example:
#Example - From the US region ingress.private.coralogix.us #To vpce-123456789-dksadkr123.vpce-svc-0ac1a755dfuqd40c.eu-west-1.vpce.amazonaws.com
|Github||Coralogix Open Source Integrations|
Coralogix OpenTelemetry Exporter
|Documentation||Coralogix Amazon Web Services (AWS) Lambda Telemetry Exporter|
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].