Add gov site caution to serverless agentic onboarding sections (#39362)

* Add gov site caution to serverless agentic onboarding sections

Add a US1-FED/US2-FED "not supported" caution to the agentic onboarding
sections of AWS Lambda, GCP Cloud Run containers, GCP Cloud Run functions,
and Azure Container Apps. Also move the AWS Lambda section above
Instrumentation instructions.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Update hugo/content/en/serverless/aws_lambda/instrumentation/_index.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Add gov caution under Quick start and rename Lambda instrumentation heading

Add the US1-FED/US2-FED caution under Quick start on the AWS Lambda page,
and rename the "Instrumentation instructions" heading to "Manual Instrumentation".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: 3 people

hugo/content/en/serverless/aws_lambda/instrumentation/_index.md

@@ -27,35 +27,22 @@ Instrument your AWS Lambda applications with a Datadog Lambda Extension to colle
 
 ## Quick start
 
+{{< site-region region="gov,gov2" >}}
+<div class="alert alert-danger">This feature is not supported for your selected <a href="/getting_started/site">Datadog site</a> ({{< region-param key="dd_site_name" >}}).</div>
+{{< /site-region >}}
+
 To get started, [sign up for a Datadog account][1] if you don’t already have one. Then, follow the [in-app installation flow in Fleet Automation][8] for AWS Lambda to instrument your Lambda functions. This quick-start configuration enables your functions to send real-time metrics, logs, and traces to Datadog.
 
 A sample application is [available on GitHub][6] with instructions on how to deploy with multiple runtimes and infrastructure-as-code tools.
 
-The quick start process configures your Lambda functions on the fly. To instrument Lambda functions permanently, see the detailed instructions in the next section.
-
-## Instrumentation instructions
-
-{{< card-grid card_width="30%" image_width="200" >}}
-  {{< image-card href="/serverless/installation/python/" src="integrations_logos/python.png" alt="Python" >}}
-  {{< image-card href="/serverless/installation/nodejs/" src="integrations_logos/nodejs.png" alt="Node.js" >}}
-  {{< image-card href="/serverless/installation/ruby/" src="integrations_logos/ruby.png" alt="Ruby" >}}
-  {{< image-card href="/serverless/installation/java/" src="integrations_logos/java.png" alt="Java" >}}
-  {{< image-card href="/serverless/installation/go/" src="integrations_logos/go-metro.png" alt="go" >}}
-  {{< image-card href="/serverless/installation/dotnet/" src="integrations_logos/dotnet_text.png" alt=".NET" >}}
-{{< /card-grid >}}
-
-## Advanced configurations
-
-After you're done with instrumentation and you've set up telemetry collection, you can use [Configure Serverless Monitoring for AWS Lambda][3] to:
-
-- connect your metrics, traces, and logs using tags
-- collect telemetry from AWS resources such as API Gateway, AppSync, and Step Functions
-- capture the request and response payloads for individual Lambda invocations
-- link errors of your Lambda functions to your source code
-- filter or scrub sensitive information from logs or traces
+The quick start process configures your Lambda functions on the fly. To instrument Lambda functions permanently, see the sections below for agentic onboarding or manual instrumentation.
 
 ## Set up with agentic onboarding
 
+{{< site-region region="gov,gov2" >}}
+<div class="alert alert-danger">This feature is not supported for your selected <a href="/getting_started/site">Datadog site</a> ({{< region-param key="dd_site_name" >}}).</div>
+{{< /site-region >}}
+
 Use agentic onboarding to set up monitoring for your Lambda functions with AI assistance. Agentic onboarding detects your project's frameworks, applies the required configuration in place, and verifies that data is flowing. Two complementary paths use the same Datadog account:
 
 - **AI Setup CLI**: A standalone terminal tool. Use it when you don't want to install an MCP server.
@@ -84,6 +71,27 @@ Help me monitor my AWS Lambda functions with Datadog.
 {{% /tab %}}
 {{< /tabs >}}
 
+## Manual Instrumentation
+
+{{< card-grid card_width="30%" image_width="200" >}}
+  {{< image-card href="/serverless/installation/python/" src="integrations_logos/python.png" alt="Python" >}}
+  {{< image-card href="/serverless/installation/nodejs/" src="integrations_logos/nodejs.png" alt="Node.js" >}}
+  {{< image-card href="/serverless/installation/ruby/" src="integrations_logos/ruby.png" alt="Ruby" >}}
+  {{< image-card href="/serverless/installation/java/" src="integrations_logos/java.png" alt="Java" >}}
+  {{< image-card href="/serverless/installation/go/" src="integrations_logos/go-metro.png" alt="go" >}}
+  {{< image-card href="/serverless/installation/dotnet/" src="integrations_logos/dotnet_text.png" alt=".NET" >}}
+{{< /card-grid >}}
+
+## Advanced configurations
+
+After you're done with instrumentation and you've set up telemetry collection, you can use [Configure Serverless Monitoring for AWS Lambda][3] to:
+
+- connect your metrics, traces, and logs using tags
+- collect telemetry from AWS resources such as API Gateway, AppSync, and Step Functions
+- capture the request and response payloads for individual Lambda invocations
+- link errors of your Lambda functions to your source code
+- filter or scrub sensitive information from logs or traces
+
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}

hugo/content/en/serverless/azure_container_apps/_index.mdoc.md

@@ -42,6 +42,12 @@ Then, choose one of two paths to instrument your application with the `serverles
 
 ## Set up with agentic onboarding
 
+{% site-region region="gov,gov2" %}
+{% alert level="danger" %}
+This feature is not supported for your selected [Datadog site](/getting_started/site) ({% region-param key="dd_site_name" /%}).
+{% /alert %}
+{% /site-region %}
+
 Two paths use the same [Datadog account][1]:
 
 - **AI Setup CLI**: A standalone terminal tool. Use it when you don't want to install an MCP server.

hugo/content/en/serverless/google_cloud_run/containers/_index.md

@@ -23,6 +23,10 @@ further_reading:
 
 ## Set up with agentic onboarding
 
+{{< site-region region="gov,gov2" >}}
+<div class="alert alert-danger">This feature is not supported for your selected <a href="/getting_started/site">Datadog site</a> ({{< region-param key="dd_site_name" >}}).</div>
+{{< /site-region >}}
+
 Use agentic onboarding to set up monitoring for your Cloud Run containers with AI assistance. Agentic onboarding detects your project's frameworks, applies the required configuration in place, and verifies that data is flowing. Two complementary paths use the same Datadog account:
 
 - **AI Setup CLI**: A standalone terminal tool. Use it when you don't want to install an MCP server.

hugo/content/en/serverless/google_cloud_run/functions/_index.md

@@ -17,6 +17,10 @@ further_reading:
 
 ## Set up with agentic onboarding
 
+{{< site-region region="gov,gov2" >}}
+<div class="alert alert-danger">This feature is not supported for your selected <a href="/getting_started/site">Datadog site</a> ({{< region-param key="dd_site_name" >}}).</div>
+{{< /site-region >}}
+
 Use agentic onboarding to set up monitoring for your Cloud Run functions with AI assistance. Agentic onboarding detects your project's frameworks, applies the required configuration in place, and verifies that data is flowing. Two complementary paths use the same Datadog account:
 
 - **AI Setup CLI**: A standalone terminal tool. Use it when you don't want to install an MCP server.