Skip to content

Add AP2 VPC Endpoint Service IDs reference table to PrivateLink docs#37461

Closed
nlopez wants to merge 7 commits into
masterfrom
pl-doc-jun11
Closed

Add AP2 VPC Endpoint Service IDs reference table to PrivateLink docs#37461
nlopez wants to merge 7 commits into
masterfrom
pl-doc-jun11

Conversation

@nlopez

@nlopez nlopez commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Adds a comprehensive DNS-to-VPC endpoint reference for AP2 customers using AWS PrivateLink.

AP2 uses a two-level DNS architecture where every customer-facing DNS record maps to a color.intake.ap2.datadoghq.com VPC endpoint address. Previously there was no documentation of this mapping, leaving customers unable to determine which VPC service endpoints to set up for the Datadog features they use.

Changes:

  • Adds a new VPC Endpoint Service IDs section (AP2-only, via site-region region="ap2") at the bottom of the PrivateLink page listing all 56 customer-facing DNS records, their color.intake anchors, and their VPC service endpoint IDs
  • Replaces the 4 existing partial 10-row tables in the setup steps (same-region, cross-region PrivateLink service names, VPC Peering service names, VPC Peering Route53) with links to the new reference section for AP2 users; US1 and AP1 users continue to see the original tables unchanged

Testing

Ran dig <fqdn> @1.1.1.1 against all 56 FQDNs in the table and confirmed every CNAME resolves to the documented color.intake.ap2.datadoghq.com anchor. Wildcard entries were resolved using star as the literal subdomain (for example, star.agent.ap2.datadoghq.com).

Result: 56/56 OK, 0 mismatches, 0 missing CNAMEs.

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

Data sourced from the AP2 DNS/LB/Color/VPC Service Endpoint DDSQL query. When US1 adopts the same pattern, the site-region guard on the new section can be extended to include us.


Co-authored with Pi (Claude Sonnet 4.6)

Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
@github-actions github-actions Bot added the Guide Content impacting a guide label Jun 11, 2026
nlopez and others added 2 commits June 11, 2026 16:40
…OC visibility

Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
- Move heading back inside site-region ap2 block so hideTOCItems()
  hides the nav entry for US1/AP1 (selector targets direct children of
  d-none site-region-container)
- Extend table-of-contents.html condition to trigger scraped-toc.html
  for pages using {{% site-region %}} (markdown shortcode), not just
  {{< site-region >}} (HTML shortcode) — scraped-toc was designed for
  exactly this case

Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Jun 11, 2026
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
@github-actions github-actions Bot removed the Architecture Everything related to the Doc backend label Jun 11, 2026
@nlopez nlopez marked this pull request as ready for review June 11, 2026 21:17
@nlopez nlopez requested a review from a team as a code owner June 11, 2026 21:17
@nlopez nlopez removed the request for review from a team June 11, 2026 21:23
Comment thread content/en/agent/guide/private-link.md Outdated
@ahmad-ddog

Copy link
Copy Markdown

Left one comment, otherwise LGTM. How did you validate the endpoints are mapped correctly? Please add your test plan in the PR summary.

nlopez and others added 2 commits June 12, 2026 09:12
@nlopez

nlopez commented Jun 12, 2026

Copy link
Copy Markdown
Contributor Author

Left one comment, otherwise LGTM. How did you validate the endpoints are mapped correctly? Please add your test plan in the PR summary.

Added Testing to PR desc!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Guide Content impacting a guide

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants