[DOCS-14689] Add UK1 PrivateLink VPC Endpoint Service IDs reference table#37668
Merged
Conversation
…age (#37431) * added callout for mnp customers on volume page * Apply suggestions from code review Co-authored-by: Olivia Shoup <116908616+OliviaShoup@users.noreply.github.com> --------- Co-authored-by: Olivia Shoup <116908616+OliviaShoup@users.noreply.github.com>
…ng setup (#37614) * Clarify assumed-role ARN requirement in WIF identity and intake mapping setup Adds warning callouts to both the identity mapping and intake mapping UI sections explaining that Datadog requires the assumed-role ARN (STS format) rather than the IAM role ARN shown in the AWS Console. Updates the Source Pattern example to show the full arn:aws:sts:: format. Adds guidance on using aws sts get-caller-identity to find the correct ARN value. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Update workload_identity_federation.md * Scope WIF warning callout to opening sentence, add aws sts tip for parity Move the ARN format list and aws sts get-caller-identity tip outside the alert div so only the opening sentence carries the warning style. Add the tip to the identity mappings warning to match the intake mappings warning. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Update Widget Share URLs docs * Restore Datadog Clipboard distinction in Widget Share URLs note Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Incorporate rtrieu and chatgpt-codex-connector's feedback --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* Add Node.js MCP client auto-instrumentation docs Document the dd-trace-js MCP client integration (@modelcontextprotocol/sdk, shipped in dd-trace 5.99.0): - Add a Node.js tab to the MCP auto-instrumentation section in mcp_client.md - Add MCP to the Node.js supported frameworks table in auto_instrumentation.md - Add a Node.js tab to the MCP integration reference (package and integration names, traced client methods) Covers client-side tracing only; server-side support is not yet available. * Chores: fix whitespace * Update Node MCP link in auto_instrumentation.md * Fix Node.js MCP run command and link to SDK setup guide - Correct the Node.js run command to invoke node explicitly (NODE_OPTIONS="--import dd-trace/initialize.mjs" node <YOUR_APP_ENTRYPOINT>) in both the auto-instrumentation and manual sections, for parity with the existing Agent Observability instrumentation guides - Add a link to the Agent Observability SDK setup guide at the end of each auto-instrumentation tab for additional configuration options * chore: use reference-style links for MCP setup guide Match the reference-link convention used elsewhere in the docs by defining the setup guide links per-tab instead of inline. --------- Co-authored-by: Janine Chan <janine.chan@datadoghq.com>
) * [FFL-2449] Add server-side flag evaluation metrics setup guide Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Update existing feature flag pages to reference evaluation metrics guide Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Add Feature Flag Graphs concepts page Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Mark feature_flag.evaluations metric as experimental in server SDK pages Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Fix Vale warnings in new content Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * clean up flag_graphs page * [FFL-2449] Add flag graphs screenshots Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * clean up server eval setup page * clean up server feature flags * clean up server feature flags pt2 * clean up SDK pages: remove DD_METRICS_OTEL_ENABLED, add further_reading links Remove DD_METRICS_OTEL_ENABLED from all server SDK pages and replace with comments pointing to the setup guide, matching the _index.md pattern. Add further_reading links to server_flag_evaluation_metrics and flag_graphs on all SDK pages. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * replace dark mode screenshots with light mode versions Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * add new Graphs page to side nav menu * [FFL-2449] Incorporate sameerank and joepeeples's feedback Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Update flag list screenshot Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [FFL-2449] Note Python tracer defaults to gRPC for OTLP --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com> Co-authored-by: Sameeran Kunche <sameeran.kunche@datadoghq.com>
Update page title, navigation, and references for the feature rename. Adds an alias from the old URL so existing links keep working.
* Batch of updates from UI review * Apply Jeff's suggestion
…able - Fill in all UK1 aws_private_link_* service names from DDSQL query (eu-west-2 VPC endpoint service IDs for all 12 private link fields) - Fill in all UK1 *_endpoint_private_link anchor addresses (color.intake.uk1.datadoghq.com values for all 8 endpoint fields) - Add UK1 VPC Endpoint Service IDs reference section to private-link.md with complete 58-row DNS-to-anchor-to-VPC-endpoint mapping table - Add UK1 'see VPC Endpoint Service IDs' link blocks in all 4 setup step locations (same-region, cross-region, VPC Peering, Route53) aws_customer_access_id.uk1 remains TODO (AWS account ID not queryable via DDSQL) Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
github-actions
Bot
added
Architecture
* Document SCIM role provisioning Add role provisioning capability to the main SCIM page, Okta role attribute mapping instructions, and the roles attribute to the Entra attribute-mapping table. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Move role provisioning behavior after prerequisites; trim capabilities Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…erence tables (#37476) * Add AP2 VPC Endpoint Service IDs reference table to PrivateLink docs Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Move VPC Endpoint Service IDs heading outside site-region block for TOC visibility Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Fix VPC Endpoint Service IDs TOC visibility for AP2 only - 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> * Revert table-of-contents.html site-region condition change Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Replace 'CNAMEs' with 'maps to' per PR feedback Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * [DOCS-14689] Add US1 PrivateLink VPC Endpoint Service IDs reference table (#37489) * [DOCS-14689] Add US1 PrivateLink VPC Endpoint Service IDs reference table Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Add orchid (api/synthetics) to US1 PrivateLink table Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Remove duplicate inline table from cross-region tab; keep single VPC Endpoint Service IDs section Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Remove legacy api.datadoghq.com --- entry; orchid color anchor confirmed in public DNS Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> --------- Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Remove redundant US1 PrivateLink service names link; update table anchor to vpc-endpoint-service-ids Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> * Apply suggestions from code review Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> * Update content/en/agent/guide/private-link.md Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> --------- Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org> Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
Contributor
…d conflicts Incorporates the merged US1+AP2 PrivateLink VPC Endpoint Service IDs PR (#37476). Conflict resolution: - Keeps master's {{% site-region region="ap1" %}} table wrappers and US1/AP2 link blocks in all 4 setup-step locations - Appends UK1 link block after US1+AP2 in each location - UK1 VPC Endpoint Service IDs table follows US1+AP2 tables at bottom No conflicts in regions.config.js (master had no uk1 entries to conflict with our filled-in values). Co-authored-by: Pi <noreply+claude-sonnet-4-6@example.org>
Contributor
|
Created DOCS-14916 for docs review. |
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
14 participants
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?
Builds on top of #37657 (UK1 datacenter support) to add complete PrivateLink endpoint data for UK1.
UK1 uses the same two-level DNS architecture as AP2: every customer-facing DNS record maps to a
color.intake.uk1.datadoghq.comVPC endpoint address. Previously, all UK1 PrivateLink values inregions.config.jswere set toTODO.Changes:
TODOvalues inregions.config.jswith real data queried from DDSQL (eu-west-2 VPC endpoint service IDs andcolor.intake.uk1.datadoghq.comanchor addresses)site-region region="uk1") at the bottom of the PrivateLink page listing all 58 customer-facing DNS records, theircolor.intakeanchors, and their VPC service endpoint IDsNote:
aws_customer_access_id.uk1remainsTODO— the AWS account ID is not queryable via DDSQL.Merge instructions
Merge readiness:
Additional notes
Depends on #37657. Should be merged after that PR.
Data sourced from DDSQL query: https://app.datadoghq.com/ddsql/editor?ddsql_dataset_id=a6b41f00-ed8f-494f-8456-1d6eb6ddac7f
Co-authored with Pi (Claude Sonnet 4.6)