This guide walks you through how to configure AWS PrivateLink for use with Datadog.
The overall process consists of configuring an internal endpoint in your VPC that local Datadog Agents can send data to. Your VPC endpoint is then peered with the endpoint within Datadog’s VPC.
dd_url parameter in your datadog.yaml:
Connect to the AWS console to region us-east-1 and create a new VPC endpoint:
Select Find service by name.
Fill the Service Name text box according to which service you want to establish AWS PrivateLink for:
|Datadog Metric Service Name|
|Forwarder||Datadog Logs Service Name|
|Datadog Agent or Lambda Extension|
|Lambda forwarder or custom forwarder|
|Datadog API Service Name|
|Datadog Process Monitoring Service Name|
|Datadog Trace Service Name|
|Datadog Kubernetes Explorer Service Name|
Hit the verify button. If it does not return Service name found, reach out to the Datadog support team.
Choose the VPC and subnets that should be peered with the Datadog VPC service endpoint.
Make sure that for Enable DNS name the Enable for this endpoint is checked:
Choose the security group of your choice to control what can send traffic to this VPC endpoint.
Note: The security group must accept inbound traffic on TCP port
Hit Create endpoint at the bottom of the screen. If successful, the following is displayed:
Click on the VPC endpoint ID to check its status.
Wait for the status to move from Pending to Available. This can take up to 10 minutes.
Once it shows Available, the AWS PrivateLink is ready to be used.
If you are collecting logs data, ensure your Agent is configured to send logs over HTTPS. If it’s not already there, add the following to the Agent
datadog.yaml configuration file:
logs_config: use_http: true
If you are using the container Agent, set the following environment variable instead:
This configuration is required when sending logs to Datadog with AWS PrivateLink. See Agent log collection for more details.
Restart your Agent to send data to Datadog through AWS PrivateLink.
To route traffic to Datadog’s PrivateLink offering in
us-east-1 from other regions, use inter-region Amazon VPC peering.
Inter-region VPC peering enables you to establish connections between VPCs across different AWS regions. This allows VPC resources in different regions to communicate with each other using private IP addresses.
See Amazon VPC peering for more details.
Additional helpful documentation, links, and articles: