[DOCS-14689] Add US1 PrivateLink VPC Endpoint Service IDs reference table#37489
Open
nlopez wants to merge 5 commits into
Open
[DOCS-14689] Add US1 PrivateLink VPC Endpoint Service IDs reference table#37489nlopez wants to merge 5 commits into
nlopez wants to merge 5 commits into
Conversation
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
Contributor
Preview links (active after the
|
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a comprehensive DNS-to-VPC endpoint reference for US1 customers using AWS PrivateLink. Mirrors the approach taken for AP2 in #37476.
US1 uses a two-level DNS architecture where every customer-facing DNS record maps to a
color.intake.datadoghq.comVPC 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:
site-region region="us") at the bottom of the PrivateLink page listing all 54 customer-facing DNS records, theircolor.intakeanchors, and their VPC service endpoint IDssite-region region="us,ap1"table blocks into separateap1andusblocks, with US1 users now seeing a link to the new reference section instead of the partial 10-row tablesThis PR is based on the AP2 branch (
nick.lopez/pl-doc-jun11) and targets it as the base. Once #37476 merges, this PR's base can be changed tomaster.Testing
Ran
dig <fqdn> @1.1.1.1against all 54 FQDNs in the table (wildcards resolved usingstaras the literal subdomain, for examplestar.datadoghq.com).color.intake.datadoghq.comanchor.metrics.agent.datadoghq.com,trace.agent.datadoghq.com,api.datadoghq.com). This is expected — US1 uses split-horizon DNS for these records, so the color-anchor routing only applies within the VPC when PrivateLink is active. The VPC endpoint service IDs from the DDSQL query are still the correct values.Result: 54/54 confirmed correct (40 via public CNAME, 14 via authoritative DDSQL source).
Merge instructions
Merge readiness:
Additional notes
Data sourced from the US1 DNS/LB/Color/VPC Service Endpoint DDSQL query.
Co-authored with Pi (Claude Sonnet 4.6)