AWS devopsagent documentation change
Summary
Updated Datadog integration documentation with corrected grammar, added detailed endpoint table for different Datadog sites, changed 'Remove from agent space' to 'Deregister from account', and updated section reference from 'Connecting New Relic' to 'Connecting Grafana'
Security assessment
The changes provide clearer documentation for Datadog endpoint configuration across different regions/sites, which helps prevent misconfiguration but doesn't address a specific security vulnerability. The endpoint table addition improves operational clarity but isn't a security fix. No evidence of security issue remediation.
Diff
diff --git a/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md b/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md index 4602af2b0..ec8885581 100644 --- a//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md +++ b//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-datadog.md @@ -13 +13 @@ Currently, AWS DevOps Agent supports Datadog users with built-in, 1 way integrat - * **Automated Investigation triggering -** Datadog events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. + * **Automated Investigation triggering** \- Datadog events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. @@ -15 +15 @@ Currently, AWS DevOps Agent supports Datadog users with built-in, 1 way integrat - * **Telemetry introspection** \- AWS DevOps Agent can introspect Datadog telemetry as it investigates an issue via the each providers remote MCP server. + * **Telemetry introspection** \- AWS DevOps Agent can introspect Datadog telemetry as it investigates an issue via each provider's remote MCP server. @@ -36 +36 @@ Establish connection to your Datadog remote MCP endpoint with account access cre - * **Endpoint URL** \- Your Datadog MCP server endpoint (typically [https://mcp.datadoghq.com/api/unstable/mcp-server/mcp](https://mcp.datadoghq.com/api/unstable/mcp-server/mcp)) + * **Endpoint URL** \- Your Datadog MCP server endpoint. The endpoint URL varies depending on your Datadog site. See the Datadog site endpoint table below. @@ -46,0 +47,13 @@ Establish connection to your Datadog remote MCP endpoint with account access cre +#### Datadog site endpoints + +The MCP endpoint URL varies depending on your Datadog site. To identify your site, check the URL in your browser when logged into Datadog, or see [Access the Datadog site](https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site). + +Datadog Site | Site Domain | MCP Endpoint URL +---|---|--- +US1 (default) | `datadoghq.com` | `https://mcp.datadoghq.com/api/unstable/mcp-server/mcp` +US3 | `us3.datadoghq.com` | `https://mcp.us3.datadoghq.com/api/unstable/mcp-server/mcp` +US5 | `us5.datadoghq.com` | `https://mcp.us5.datadoghq.com/api/unstable/mcp-server/mcp` +EU1 | `datadoghq.eu` | `https://mcp.datadoghq.eu/api/unstable/mcp-server/mcp` +AP1 | `ap1.datadoghq.com` | `https://mcp.ap1.datadoghq.com/api/unstable/mcp-server/mcp` +AP2 | `ap2.datadoghq.com` | `https://mcp.ap2.datadoghq.com/api/unstable/mcp-server/mcp` + @@ -140 +153 @@ The telemetry source is connected at two levels at the agent space level and at -### Step 2: Remove from agent space +### Step 2: Deregister from account @@ -161 +174 @@ Connecting Dynatrace -Connecting New Relic +Connecting Grafana