Endpoints and deployment
Use this page as a reference when configuring or validating Coralogix PrivateLink connectivity. Configuration instructions are covered in the PrivateLink guides.
When using AWS PrivateLink, you must update your Coralogix endpoints to use the private DNS names and the corresponding AWS PrivateLink service names.
For example, if your Coralogix domain is ap1.coralogix.com and you are configuring access to the Coralogix API:
- Use the private DNS name
api.private.ap1.coralogix.com - Use the AWS service name
com.amazonaws.vpce.ap-south-1.vpce-svc-06114eda4b29cf966
Coralogix exposes AWS PrivateLink endpoint services in all supported Coralogix AWS regions.
PrivateLink endpoints
Coralogix provides separate PrivateLink services for different traffic types. Each traffic type has its own service name and private DNS name.
The supported API types are:
- api: Coralogix public APIs and control-plane operations
- private-ingress: Log, metric, and trace ingestion traffic
- syslog: Syslog-based ingestion
When creating a VPC endpoint, ensure you select the service that matches the traffic type used by your integration.
Use the domain selector at the right corner of the page to display the correct DNS and service name table for your Coralogix domain.
PrivateLink endpoints
Dynamic regional information
The table updates based on your selected domain. Use the domain selector in the upper-right corner to switch regions.
Selected region: — AWS region , .
| API type | Private DNS | Service name |
|---|---|---|
| api | api.private. | |
| private-ingress | ingress.private. | |
| syslog | syslog.private. |
Use these values when:
- Creating or verifying an Interface VPC endpoint
- Configuring application endpoints to use Coralogix private DNS
- Validating that traffic is routed through PrivateLink
PrivateLink deployments
For high availability, Coralogix deploys its PrivateLink services across multiple Availability Zones in each region. The information in the table below is provided for visibility and operational reference.
Note
When creating your VPC endpoint, you do not need to match Coralogix’s Availability Zones. AWS automatically routes traffic between the Availability Zones you select and Coralogix’s service Availability Zones.
| Environment | Region | Availability Zones |
|---|---|---|
| STG1 | eu-west-1 | euw1-az3 (eu-west-1a), euw1-az1 (eu-west-1b) |
| EU2 | eu-north-1 | eun1-az1 (eu-north-1a), eun1-az2 (eu-north-1b) |
| EU1 | eu-west-1 | euw1-az2 (eu-west-1a), euw1-az3 (eu-west-1b) |
| AP1 | ap-south-1 | aps1-az1 (ap-south-1a), aps1-az3 (ap-south-1b) |
| AP2 | ap-southeast-1 | apse1-az1 (ap-southeast-1a), apse1-az2 (ap-southeast-1b) |
| US1 | us-east-2 | use2-az1 (us-east-2a), use2-az2 (us-east-2b) |
| US2 | us-west-2 | usw2-az2 (us-west-2a), usw2-az1 (us-west-2b) |
| AP3 | ap-southeast-3 | apse3-az1 (ap-southeast-3a), apse3-az2 (ap-southeast-3b) |
AWS partition considerations
Native cross-region PrivateLink connectivity, and the endpoints listed on this page, require that both the consumer VPC and the Coralogix service reside in the same AWS partition.
For example:
- Standard commercial regions can connect to other standard regions
- GovCloud and China partitions cannot connect to standard regions using native PrivateLink
Legacy PrivateLink endpoints
Legacy PrivateLink endpoints are maintained for backward compatibility only.
New configurations should use the region-specific PrivateLink endpoints listed above.
A complete table of legacy endpoints for reference:
| Coralogix domain | Coralogix AWS region | Service name | OpenTelemetry (traces, metrics, logs) | Coralogix Lambda telemetry | Coralogix logs | Prometheus Remote Write |
|---|---|---|---|---|---|---|