# AWS PrivateLink

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

Use this page to understand how [AWS PrivateLink](https://aws.amazon.com/privatelink/) works with Coralogix and to choose the correct connectivity model before starting configuration.

AWS PrivateLink provides private, highly available connectivity between your VPC and Coralogix services, as if Coralogix were hosted directly inside your network. In this model, Coralogix acts as the service provider, and your AWS account acts as the consumer.

<!-- -->

PrivateLink supports connectivity from:

* EC2 and container-based workloads running in a VPC
* AWS Lambda functions configured for VPC access
* On-premises networks connecting through a VPN or AWS Direct Connect, allowing them to access services as if they were hosted directly in the local network.
* Other AWS Services and SaaS products, which can act as consumers connecting to endpoint services

## Core concepts[​](#core-concepts "Direct link to Core concepts")

### Private connectivity[​](#private-connectivity "Direct link to Private connectivity")

All traffic stays within the AWS network and does not traverse the public internet. Internet gateways, NAT gateways, and public IPs are not required.

### Interface VPC endpoints[​](#interface-vpc-endpoints "Direct link to Interface VPC endpoints")

Coralogix uses Interface type VPC endpoints. When you create an endpoint, AWS creates endpoint network interfaces (ENIs) with private IP addresses in the subnets you select. These ENIs are the private entry points to Coralogix.

Workloads such as EC2, containers, and Lambda functions send traffic to Coralogix through these endpoint ENIs.

### Security and policy controls[​](#security-and-policy-controls "Direct link to Security and policy controls")

Access is controlled using:

* Security groups attached to ENIs
* VPC endpoint policies (IAM resource policies)

## What you will configure[​](#what-you-will-configure "Direct link to What you will configure")

All connectivity models follow the same high-level flow:

1. Identify the Coralogix PrivateLink service that matches your Coralogix domain. Learn more in our Coralogix PrivateLink endpoints and deployment guide.
2. Create an Interface VPC endpoint.
3. Enable private DNS resolution.
4. Validate connectivity from workloads inside your VPC.

## Choose your connectivity model[​](#choose-your-connectivity-model "Direct link to Choose your connectivity model")

Use the following flowchart to determine which PrivateLink setup guide best suits your needs.

<!-- -->

## Lambda-specific considerations (high level)[​](#lambda-specific-considerations-high-level "Direct link to Lambda-specific considerations (high level)")

When using AWS Lambda with PrivateLink:

* The Lambda function must be attached to a VPC

* Lambda creates requester-managed ENIs in the selected subnets

* Additional endpoints may be required:

  <!-- -->

  * S3 Gateway Endpoint (if the integration uses Amazon S3)
  * Secrets Manager Interface Endpoint (if using AWS Secrets Manager)

Detailed Lambda configuration steps are covered in the Lambda Configuration guide.

## Native cross-region considerations[​](#native-cross-region-considerations "Direct link to Native cross-region considerations")

When using native cross-region PrivateLink:

* The IAM principal creating the endpoint must have the `vpce:AllowMultiRegion` permission
* Both regions must belong to the same AWS partition
* Availability Zones do not need to match Coralogix’s AZs
* Inter-AZ traffic via PrivateLink endpoints is free, which can significantly reduce costs for high-volume telemetry

## Use PrivateLink with Coralogix integrations[​](#use-privatelink-with-coralogix-integrations "Direct link to Use PrivateLink with Coralogix integrations")

Visit the k8s and ecs-ec2 integration pages to learn how to enable PrivateLink in the integrations using a single toggle.