Connect to Datadog over AWS PrivateLink

1. Connect the AWS Console to region us-east-1 and create a VPC endpoint.

2. Select Find service by name.

3. Fill the Service Name text box according to which service you want to establish AWS PrivateLink for:

4. Click Verify. If this does not return Service name found, reach out to Datadog support.

5. Choose the VPC and subnets that should be peered with the Datadog VPC service endpoint.

6. Make sure that for Enable DNS name, Enable for this endpoint is checked:

7. 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 443.

8. Click Create endpoint at the bottom of the screen. If successful, the following is displayed:

9. Click on the VPC endpoint ID to check its status.

10. Wait for the status to move from Pending to Available. This can take up to 10 minutes. Once it shows Available, you can use AWS PrivateLink.

11. If you are collecting logs data, ensure your Agent is configured to send logs over HTTPS. If the data is 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:

    DD_LOGS_CONFIG_USE_HTTP=true
    

    This configuration is required when sending logs to Datadog with AWS PrivateLink and the Datadog Agent, and is not required for the Lambda Extension. For more details, see Agent log collection.

12. If your Lambda Extension loads the Datadog API Key from AWS Secrets Manager using the ARN specified by the environment variable DD_API_KEY_SECRET_ARN, you need to create a VPC endpoint for Secrets Manager.

13. Restart your Agent to send data to Datadog through AWS PrivateLink.

Amazon VPC peering

1. Connect the AWS Console to region us-east-1 and create a VPC endpoint.

2. Select Find service by name.
3. Fill the Service Name text box according to the service you want to establish AWS PrivateLink for:

4. Click Verify. If this does not return Service name found, reach out to Datadog support.

5. Next, choose the VPC and subnets that should be peered with the Datadog VPC service endpoint. Do not select Enable DNS name as VPC peering requires DNS to be manually configured.

6. 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 443.

7. Click Create endpoint at the bottom of the screen. If successful, the following is displayed:

8. Click on the VPC endpoint ID to check its status.
9. Wait for the status to move from Pending to Available. This can take up to 10 minutes.
10. Once this is created, route traffic from another region to send the data to Datadog using private link. For more information, see the Work With VPC Peering connections AWS documentation.

Amazon Route53

1. Create a Route53 private hosted zone for each service you have created an AWS PrivateLink endpoint for. Attach the private hosted zone to the VPC in us-east-1.

Use the list below to map service and DNS name to different parts of Datadog:

You can also find this information by interrogating the AWS API, DescribeVpcEndpointServices, or by using the following CLI command: aws ec2 describe-vpc-endpoint-services --service-names <service-name>.

For example, in the case of the Datadog metrics endpoint:

aws ec2 describe-vpc-endpoint-services --service-names com.amazonaws.vpce.us-east-1.vpce-svc-09a8006e245d1e7b8 | jq '.ServiceDetails[0].PrivateDnsName'

This returns metrics.agent.datadoghq.com, the private hosted zone name that you need in order to associate with the VPC which the Agent traffic originates in. Overriding this record grabs all Metrics-related intake hostnames.

2. Within each new Route53 private hosted zone, create an A record with the same name. Toggle the Alias option, then under Route traffic to, choose Alias to VPC endpoint, us-east-1, and enter the DNS name of the VPC endpoint associated with the DNS name.

   Note: To retrieve your DNS name, see the View endpoint service private DNS name configuration documentation.

3. Configure VPC peering and routing between the VPC in us-east-1 that contains the Datadog PrivateLink endpoints and the VPC in the region where the Datadog Agents run.

4. If the VPCs are in different AWS accounts, the VPC containing the Datadog Agent must be authorized to associate with the Route53 private hosted zones before continuing. Create a VPC association authorization for each Route53 private hosted zone using the region and VPC ID of the VPC where the Datadog Agent runs. This option is not available in the AWS Console. It must be configured using the AWS CLI, SDK, or API.

5. Edit the Route53 hosted zone to add the non-us-east-1 VPC.

6. VPCs that have the Private Hosted Zone (PHZ) attached need to have certain settings toggled on, specifically enableDnsHostnames and enableDnsSupport in the VPCs that the PHZ is associated with. See Considerations when working with a private hosted zone.

7. Restart the Agent to send data to Datadog through AWS PrivateLink.

Troubleshooting DNS resolution and connectivity

The DNS names should resolve to IP addresses contained within the CIDR block of the VPC in us-east-1, and connections to port 443 should succeed.

If DNS is resolving to public IP addresses, then the Route53 zone has not been associated with the VPC in the alternate region, or the A record does not exist.

If DNS resolves correctly, but connections to port 443 are failing, then VPC peering or routing may be misconfigured, or port 443 may not be allowed outbound to the CIDR block of the VPC in us-east-1.

The VPCs with Private Hosted Zone (PHZ) attached need to have a couple of settings toggled on. Specifically, enableDnsHostnames and enableDnsSupport need to be turned on in the VPCs that the PHZ is associated with. See Amazon VPC settings.

Datadog Agent

1. If you are collecting logs data, ensure your Agent is configured to send logs over HTTPS. If the data is not already there, add the following to the Agent datadog.yaml configuration file:

   logs_config:
       force_use_http: true
   

   If you are using the container Agent, set the following environment variable instead:

   DD_LOGS_CONFIG_FORCE_USE_HTTP=true
   

   This configuration is required when sending logs to Datadog with AWS PrivateLink and the Datadog Agent, and is not required for the Lambda Extension. For more details, see Agent log collection.

2. If your Lambda Extension loads the Datadog API Key from AWS Secrets Manager using the ARN specified by the environment variable DD_API_KEY_SECRET_ARN, you need to create a VPC endpoint for Secrets Manager.

3. Restart the Agent.