AWS devopsagent documentation change
Summary
Replaced detailed webhook configuration instructions with a reference to centralized documentation for bearer token authentication.
Security assessment
The change consolidates authentication documentation but doesn't address a specific vulnerability. It promotes secure practices by standardizing bearer token usage.
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 6e361ac48..14765eea0 100644 --- a//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md +++ b//devopsagent/latest/userguide/connecting-telemetry-sources-connecting-new-relic.md @@ -80,26 +80 @@ Using the Webhook URL and API Key you can configure New Relic to send events to -To ensure that events sent can be used by the DevOps Agent, make sure that the data transmitted to the webhook matches the data schema specified below. Events that do not match this schema may be ignored by DevOps Agent. - -Set the method and the headers - - - method: "POST", - headers: { - "Content-Type": "application/json", - "Authorization": "Bearer <Token>", - }, - -Send the body as a JSON string. - - - { - eventType: 'incident'; - incidentId: string; - action: 'created' | 'updated' | 'closed' | 'resolved'; - priority: "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "MINIMAL"; - title: string; - description?: string; - timestamp?: string; - service?: string; - // The original event generated by service is attached here. - data?: object; - } +New Relic webhooks use bearer token authentication. For the complete webhook request format, payload schema, and example code, see [Invoking DevOps Agent through Webhook](./configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.html). Use the Version 2 (Bearer token authentication) examples, setting the `Authorization: Bearer <Token>` header with the API Key from Step 2.