1. Connect the AWS Management Console to the region of your choice.

2. From the VPC Dashboard, under PrivateLink and Lattice, select Endpoints.

3. Click Create Endpoint:

4. Configure the VPC interface endpoint settings

   1. Optionally, fill in the Name tag.
   2. Under Type, select PrivateLink Ready partner services.

5. Discover and configure the interface endpoint with cross-region support:

   1. Under Service name, fill in the service name with a valid PrivateLink service name from the table below.
   2. Under Service region, click Enable Cross Region endpoint and select .
   3. Click Verify service and wait for a Service name verified notification. Note: If you aren’t able to verify the service after completing the steps above, reach out to Datadog Support.

6. Under Network Settings, select a VPC to deploy the VPC Interface endpoint with.

7. Ensure the option to Enable DNS name is checked.

8. Under Subnets, select one or more subnets in your VPC for the interface endpoint.

9. Under Security Groups, select a security group to control what can send traffic to the VPC endpoint.

   Note: The security group must accept inbound traffic on TCP port 443.

10. Optionally, provide a Name tag and click Create endpoint.

11. Allow a few minutes for the endpoint status to update from Pending to Available. This may take up to 10 minutes. If it is taking longer than expected, reach out to Datadog Support.

After the endpoint status is updated to Available, you can use this endpoint to send telemetry to Datadog using the cross-region AWS PrivateLink endpoint.

PrivateLink service names

Note: Cross-region PrivateLink doesn’t emit CloudWatch metrics. See CloudWatch metrics for AWS PrivateLink for more information.

1. Connect the AWS Console to region 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. After creating the endpoint, use VPC peering to make the PrivateLink endpoint available in another region to send telemetry to Datadog over PrivateLink. For more information, read the Work With VPC Peering connections page in AWS.

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 .

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 command:

aws ec2 describe-vpc-endpoint-services --service-names <service-name>`

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

aws ec2 describe-vpc-endpoint-services --service-names  | jq '.ServiceDetails[0].PrivateDnsName'

This returns metrics.agent., 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, , and enter the DNS name of the VPC endpoint associated with the DNS name.

   Notes:

   • To retrieve your DNS name, see the View endpoint service private DNS name configuration documentation.
   • The Agent sends telemetry to versioned endpoints, for example, [version]-app.agent. which resolves to metrics.agent. through a CNAME alias. Therefore, you only need to set up a private hosted zone for metrics.agent..

3. Configure VPC peering and routing between the VPC in 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 VPCs for other regions.

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

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.