[DOCS-14086] US2-FED update#36153
Merged
Merged
Conversation
Add the US2-FED (IL5) GovCloud data center as region code gov2 across site configuration and content. Updates regions.config.js with derived endpoints, params.yaml allowedRegions and unsupported_sites, the site access table in getting_started, and region-conditional blocks across content/en. Splits blocks containing hardcoded US1-FED values (SDK site enums, URLs, site strings) into dedicated gov2 blocks with US2-FED equivalents. Flags FIPS Agent support for US2-FED in the FIPS compliance page and marks the legacy FIPS Proxy as US2-FED-unsupported. Private-link endpoints, AWS VPCE service names, the oncall domain color, and the rate-limit dashboard IDs are left as TODO pending values from the infra team. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
github-actions
Bot
added
Architecture
Contributor
Government sites share the US1 oncall domain (navy) and do not support AWS PrivateLink. Replace the US2-FED TODOs with the correct gov equivalents: navy oncall, N/A for aws_private_link_cross_region, "not supported" for all aws_private_link_*_service_name keys, and the regular endpoint as the fallback for *_endpoint_private_link keys (matching the US1-FED pattern). Also apply gov2 region handling to the Cdocs .mdoc.md sources (and related partials under layouts/shortcodes/mdoc/en/sdk/) that feed the gitignored SDK and RUM setup pages, so the rebuilt .md artifacts pick up the new region. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Dashboard integration IDs are site-specific and must be looked up in each web app. Rather than ship a broken TODO link, omit the US2-FED entry entirely (matching the existing precedent where AP2 is not listed). A follow-up can add the gov2 entry once the US2-FED dashboard ID is known. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Lost during a merge conflict resolution. The AI summaries and smart chapters banner uses only region-param shortcodes, so it's safe to keep gov and gov2 in the same comma list. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
A few content updates slipped through the initial US2-FED sweep: - Two MCP Server pages added by a recent PR had "not supported" banners scoped to gov only; extended to gov,gov2 since both are listed as unsupported in params.yaml. - A PowerShell metrics example, a react-native codepush comment, and an Android SDK site parameter table row listed US1-FED but not US2-FED. - The getting-started/site page's "select US1-FED" prompt now mentions both gov sites. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
content/en/dd_e2e/ holds Playwright e2e test fixtures (draft: true). These shouldn't be updated as part of DC rollouts - the test expects stable content. Skill and inventory script updated in a separate commit to skip this directory automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
hestonhoffman
marked this pull request as ready for review
April 23, 2026 22:45
hestonhoffman
changed the title
Row had app.ddog-gov.com (copied from US1-FED); should be us2.ddog-gov.com per the IL5 Deployment Guide's published vanity URL. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
domalessi
approved these changes
Apr 23, 2026
domalessi
left a comment
domalessi
left a comment
Contributor
There was a problem hiding this comment.
Approved for the mdoc files!
jaygorrell
reviewed
Apr 24, 2026
jaygorrell
left a comment
jaygorrell
left a comment
Member
There was a problem hiding this comment.
I'm not familiar with this content but I gave it a pass based on patterns and areas I recongize. I flagged a few things that stood out for attention from someone that knows more about this :)
davidejones
approved these changes
Apr 24, 2026
domalessi
approved these changes
Apr 24, 2026
domalessi
left a comment
domalessi
left a comment
Contributor
There was a problem hiding this comment.
Looks good, Heston! Left a few small suggestions, but nothing blocking.
Co-authored-by: domalessi <[email protected]>
Co-authored-by: domalessi <[email protected]>
estherk15
pushed a commit
that referenced
this pull request
May 4, 2026
* [DOCS-14086] Add US2-FED data center Add the US2-FED (IL5) GovCloud data center as region code gov2 across site configuration and content. Updates regions.config.js with derived endpoints, params.yaml allowedRegions and unsupported_sites, the site access table in getting_started, and region-conditional blocks across content/en. Splits blocks containing hardcoded US1-FED values (SDK site enums, URLs, site strings) into dedicated gov2 blocks with US2-FED equivalents. Flags FIPS Agent support for US2-FED in the FIPS compliance page and marks the legacy FIPS Proxy as US2-FED-unsupported. Private-link endpoints, AWS VPCE service names, the oncall domain color, and the rate-limit dashboard IDs are left as TODO pending values from the infra team. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * Update FIPS doc * [DOCS-14086] Resolve PrivateLink/oncall TODOs and update mdoc sources Government sites share the US1 oncall domain (navy) and do not support AWS PrivateLink. Replace the US2-FED TODOs with the correct gov equivalents: navy oncall, N/A for aws_private_link_cross_region, "not supported" for all aws_private_link_*_service_name keys, and the regular endpoint as the fallback for *_endpoint_private_link keys (matching the US1-FED pattern). Also apply gov2 region handling to the Cdocs .mdoc.md sources (and related partials under layouts/shortcodes/mdoc/en/sdk/) that feed the gitignored SDK and RUM setup pages, so the rebuilt .md artifacts pick up the new region. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * [DOCS-14086] Drop US2-FED rate-limit dashboard link pending ID Dashboard integration IDs are site-specific and must be looked up in each web app. Rather than ship a broken TODO link, omit the US2-FED entry entirely (matching the existing precedent where AP2 is not listed). A follow-up can add the gov2 entry once the US2-FED dashboard ID is known. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * (DOCS-12567) Insert banners conditionally * Site page edit * Fix Rate limit pages * [DOCS-14086] Re-add gov2 to session_replay AI-features banner Lost during a merge conflict resolution. The AI summaries and smart chapters banner uses only region-param shortcodes, so it's safe to keep gov and gov2 in the same comma list. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * [DOCS-14086] Catch stragglers missed on first pass A few content updates slipped through the initial US2-FED sweep: - Two MCP Server pages added by a recent PR had "not supported" banners scoped to gov only; extended to gov,gov2 since both are listed as unsupported in params.yaml. - A PowerShell metrics example, a react-native codepush comment, and an Android SDK site parameter table row listed US1-FED but not US2-FED. - The getting-started/site page's "select US1-FED" prompt now mentions both gov sites. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * [DOCS-14086] Revert dd_e2e test fixture change content/en/dd_e2e/ holds Playwright e2e test fixtures (draft: true). These shouldn't be updated as part of DC rollouts - the test expects stable content. Skill and inventory script updated in a separate commit to skip this directory automatically. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * [DOCS-14086] Fix US2-FED site URL in access table Row had app.ddog-gov.com (copied from US1-FED); should be us2.ddog-gov.com per the IL5 Deployment Guide's published vanity URL. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * Apply suggestions from code review Co-authored-by: domalessi <[email protected]> * Apply suggestions from code review Co-authored-by: domalessi <[email protected]> --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]> Co-authored-by: domalessi <[email protected]>
This was referenced May 5, 2026
gh-worker-dd-mergequeue-cf854d Bot
pushed a commit
to DataDog/datadog-operator
that referenced
this pull request
May 6, 2026
Use dynamic region-param for global.site description Replace the hardcoded list of Datadog sites in the global.site parameter description with a dynamic region-param shortcode. This renders the correct site value per the reader's selected region on docs.datadoghq.com, and automatically covers new data centers without requiring manual updates to this file. Related: DataDog/documentation#36153 (DOCS-14086) Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> Add overide and generate Fix curly quotes Apply suggestions from code review Co-authored-by: Bryce Eadie <[email protected]> Regenerate docs Co-authored-by: heston.hoffman <[email protected]>
oacharles
pushed a commit
to modal-labs/integrations-extras
that referenced
this pull request
May 14, 2026
… docs (DataDog#2992) * Add US2-FED (gov2) region to LaunchDarkly integration docs Add gov2 to the comma-separated region list in the site-region shortcode block in the LaunchDarkly README. US2-FED is a new Datadog GovCloud data center (IL5). Related: DataDog/documentation#36153 (DOCS-14086) Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * Remove site-support banner from LaunchDarkly README Site-support banners should be managed centrally in the documentation repo's params.yaml (unsupported_sites), not inline in integration README files. A corresponding PR in DataDog/documentation will add the unsupported_sites entry. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
apurvagandhi
pushed a commit
to fidelity-contributions/datadog-integrations-core
that referenced
this pull request
May 14, 2026
…3604) * Add US2-FED (gov2) region to integration site-region blocks Add gov2 to the comma-separated region lists in site-region shortcode blocks across 4 integration README files (amazon_app_mesh, ecs_fargate, flink, openai). US2-FED is a new Datadog GovCloud data center (IL5). Related: DataDog/documentation#36153 (DOCS-14086) Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * Revert ecs_fargate gov2 changes pending proper endpoint split The ecs_fargate README has gov-specific blocks with hardcoded ddog-gov.datadoghq.com intake hosts. Simply adding gov2 to the comma list shows US2-FED readers the wrong host. A proper fix requires dedicated gov2 blocks with us2.ddog-gov.com endpoints across multiple code snippets. Backing out for now to avoid shipping incorrect config to US2-FED users. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
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
4 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?
Updates docs for US2-FED
Merge instructions
Merge readiness:
Additional notes