[DOCS-] Add AWS PrivateLink section to OP Datadog destination (DataDog#30462)

maycmlee · joepeeples · web-flow · commit be5110f23f53 · 2025-07-17T12:15:32.000-04:00
* add aws privatelink

* add live capture endpoint

* Apply suggestions from code review

Co-authored-by: Joe Peeples &lt;joe.peeples@datadoghq.com&gt;

---------

Co-authored-by: Joe Peeples &lt;joe.peeples@datadoghq.com&gt;
diff --git a/content/en/observability_pipelines/destinations/datadog_logs.md b/content/en/observability_pipelines/destinations/datadog_logs.md
@@ -3,7 +3,7 @@ title: Datadog Logs Destination
 disable_toc: false
 ---
 
-Use Observability Pipelines' Datadog Logs destination to send logs to Datadog Log Management.
+Use Observability Pipelines' Datadog Logs destination to send logs to Datadog Log Management. You can also use [AWS PrivateLink](#aws-privatelink) to send logs from Observability Pipelines to Datadog.
 
 ## Setup
 
@@ -27,5 +27,17 @@ A batch of events is flushed when one of these parameters is met. See [event bat
 |----------------|-----------------|---------------------|
 | 1,000          | 4,250,000       | 5                   |
 
+## AWS PrivateLink
+
+To send logs from Observability Pipelines to Datadog using AWS PrivateLink, see [Connect to Datadog over AWS PrivateLink][3] for setup instructions. The two endpoints you need to set up are:
+
+- Logs (User HTTP intake): `http-intake.logs.datadoghq.com`
+- Remote Configuration: `config.datadoghq.com`
+
+**Notes**:
+- If you are a PCI-compliant organization, the Worker sends logs over `http-intake-pci.logs.datadoghq.com`, which is not available as an AWS PrivateLink endpoint.
+- The `obpipeline-intake.datadoghq.com` endpoint is used for Live Capture and is not available as a PrivateLink endpoint.
+
 [1]: https://app.datadoghq.com/observability-pipelines
-[2]: /observability_pipelines/destinations/#event-batching
+[2]: /observability_pipelines/destinations/#event-batching
+[3]: /agent/guide/private-link/?tab=crossregionprivatelinkendpoints
