AWS devopsagent documentation change
Summary
Updated New Relic integration documentation with formatting fixes, corrected terminology, added clarification about webhook authorization options (Bearer token vs custom header), and changed 'Remove from agent space' to 'Deregister from account'
Security assessment
The change adds documentation about proper authorization methods for webhooks, specifically mentioning Bearer token authentication as an option. This improves security documentation by clarifying authentication best practices, but doesn't address a specific security issue or vulnerability. The addition of proper authorization guidance enhances security awareness.
Diff
diff --git a/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md b/devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md index c61fe0072..00894a233 100644 --- a//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md +++ b//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md @@ -13 +13 @@ Currently, AWS DevOps Agent supports New Relic users with built-in, 1 way integr - * **Automated Investigation triggering -** New Relic events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. + * **Automated Investigation triggering** \- New Relic events can be configured to trigger AWS DevOps Agent incident resolution Investigations via AWS DevOps Agent webhooks. @@ -15 +15 @@ Currently, AWS DevOps Agent supports New Relic users with built-in, 1 way integr - * **Telemetry introspection** \- AWS DevOps Agent can introspect New Relic telemetry as it investigates an issue via the each providers remote MCP server. + * **Telemetry introspection** \- AWS DevOps Agent can introspect New Relic telemetry as it investigates an issue via each provider's remote MCP server. @@ -38 +38 @@ Please use a Full Platform User (not Basic/Core) in New relic to enable New Reli - * **Account ID:** \- Enter your New Relic account ID obtained above + * **Account ID:** Enter your New Relic account ID obtained above @@ -76 +76 @@ Activate New Relic in a specific Agent space and configure appropriate scoping -Using the Webhook URL and API Key you can configure New Relic to send events to trigger an investigation, for example from an alarm. +Using the Webhook URL and API Key you can configure New Relic to send events to trigger an investigation, for example from an alarm. For more details on setting up webhooks, see [Change tracking webhooks](https://docs.newrelic.com/docs/change-tracking/change-tracking-webhooks/). @@ -105 +105 @@ Send the body as a JSON string. -Send webhooks with New Relic [https://newrelic.com/instant-observability/webhook-notifications](https://newrelic.com/instant-observability/webhook-notifications) (note select no authorization and instead use the custom header option) +Send webhooks with New Relic [https://newrelic.com/instant-observability/webhook-notifications](https://newrelic.com/instant-observability/webhook-notifications). You can either select Bearer token for the authorization type, or select no authorization and add the `Authorization: Bearer <Token>` as a custom header instead. @@ -128 +128 @@ 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 @@ -147 +147 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Connecting DataDog +Connecting Grafana