AWS PrivateLink

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. While Coralogix monitoring traffic is always secure, PrivateLink provides stable connectivity, a reduction in traffic costs, and even greater security by maintaining data on the AWS network.

This tutorial provides AWS Coralogix PrivateLink endpoints and instructions for standard configuration.

Use cases

The primary use case for PrivateLink with Coralogix is connectivity for monitored applications running in AWS VPCs. To use Coralogix PrivateLink, you must create a VPC endpoint in the Coralogix AWS region matching your Coralogix domain. This is referred to as same-region VPC.

PrivateLink endpoints

Coralogix exposes an AWS PrivateLink endpoint in all Coralogix AWS regions.

PrivateLink endpoints

Prerequisites

• If you use an integration involving Amazon S3, you must ensure that the VPC in which your Lambda is deployed has an S3 Service Gateway configured.

• If you intend to use AWS Secrets Manager with your Lambda, you must create another VPC endpoint for the com.amazonaws.<AWS Region>.secretsmanager service. Detailed instructions can be found here.

VPC configuration

To use Coralogix PrivateLink, you must create a VPC endpoint in the Coralogix AWS region matching your Coralogix domain. This is referred to as same-region VPC. For example, the coralogix.com domain is hosted in eu-west-1. A same-region VPC must be deployed in eu-west-1.

STEP 1. Create a VPC endpoint.

• Connect to the AWS console in your Coralogix AWS region.

• Navigate to the Endpoints section.

• Click Create 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.

• You should receive the following message: Service name verified.

• If you do not receive this message, contact us via our in-app chat or by sending us an email at support@coralogix.com.

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.

• The security group must accept inbound traffic in port 443 (TCP).

STEP 8. Click Create endpoint.

STEP 9. Verify your configuration.

• Ensure the VPC endpoint status appears as Available.

STEP 10. Connect to the VPC network.

Validate that the endpoint is working with either the following:

1. Connected VPC to a running workload (e.g. ec2 instance) and enter the following command, adjusted per cross-region:

# example US region
# telnet ingress.private.us1.coralogix.com
telnet <ingress.private.<region-domain> 443

1. Try sending a test log using the Coralogix REST API /singles ```

Next Steps

• If your AWS resources are in a different region than your Coralogix domain, you have two options:
• VPC Peering: Deploy your Lambda function using VPC peering with a cross-region VPC local to the data source. Learn more in our AWS PrivateLink: VPC Peering Configuration guide.

• Native Cross-Region PrivateLink: Use AWS's native cross-region connectivity for PrivateLink, which provides a simpler alternative without complex VPC peering. Learn more in our AWS PrivateLink: Cross-Region Connectivity guide.

• Align the VPC to your Lambda. Instructions can be found here.

Previous AWS CloudWatch Metrics Processing

Next Cross-Region Connectivity

Theme

Light

light

dark