AWS devopsagent documentation change
Summary
Updated internal documentation links for Dynatrace, Splunk, New Relic, and Datadog integration guides by removing redundant path prefixes.
Security assessment
The changes are purely documentation link corrections. There is no mention of security vulnerabilities, fixes, or new security features. The updates are about webhook integration references, which are operational but not security-related.
Diff
diff --git a/devopsagent/latest/userguide/getting-started-with-aws-devops-agent-cli-onboarding-guide.md b/devopsagent/latest/userguide/getting-started-with-aws-devops-agent-cli-onboarding-guide.md index 3625bff8d..a271390ef 100644 --- a//devopsagent/latest/userguide/getting-started-with-aws-devops-agent-cli-onboarding-guide.md +++ b//devopsagent/latest/userguide/getting-started-with-aws-devops-agent-cli-onboarding-guide.md @@ -525 +525 @@ Save the returned `<SERVICE_ID>`, then associate Dynatrace (resources are option -The response will include webhook information for integration, you can trigger an investigation from Dynatrace using this webhook. For details see, [Connecting Dynatrace](./configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-dynatrace.html) +The response will include webhook information for integration, you can trigger an investigation from Dynatrace using this webhook. For details see, [Connecting Dynatrace](./connecting-telemetry-sources-connecting-dynatrace.html) @@ -568 +568 @@ Save the returned `<SERVICE_ID>`, then associate Splunk: -The response will include webhook information for integration, you can trigger an investigation from Splunk using this webhook. For details see, [Connecting Splunk](./configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-splunk.html) +The response will include webhook information for integration, you can trigger an investigation from Splunk using this webhook. For details see, [Connecting Splunk](./connecting-telemetry-sources-connecting-splunk.html) @@ -613 +613 @@ Save the returned `<SERVICE_ID>`, then associate New relic: -The response will include webhook information for integration, you can trigger an investigation from New relic using this webhook. For details see, [Connecting New Relic](./configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-new-relic.html) +The response will include webhook information for integration, you can trigger an investigation from New relic using this webhook. For details see, [Connecting New Relic](./connecting-telemetry-sources-connecting-new-relic.html) @@ -617 +617 @@ The response will include webhook information for integration, you can trigger a -Datadog must first be registered through the AWS DevOps Agent Console UI via OAuth flow before it can be associated via CLI. For details, see [Connecting DataDog](./configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-datadog.html) +Datadog must first be registered through the AWS DevOps Agent Console UI via OAuth flow before it can be associated via CLI. For details, see [Connecting DataDog](./connecting-telemetry-sources-connecting-datadog.html) @@ -643 +643 @@ Save the returned `<SERVICE_ID>`, then associate Datadog: -The response will include webhook information for integration, you can trigger an investigation from Datadog using this webhook. For details see, [Connecting DataDog](./configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-datadog.html) +The response will include webhook information for integration, you can trigger an investigation from Datadog using this webhook. For details see, [Connecting DataDog](./connecting-telemetry-sources-connecting-datadog.html)