AWS devopsagent documentation change
Summary
Updated UI terminology from 'Click' to 'Choose'. Modified webhook payload structure in the example, adding new fields like eventType, incidentId, action, priority, and service while removing affectedResources.
Security assessment
Terminology changes are non-functional. The payload modification updates field names and structure but doesn't introduce or modify security features like authentication, encryption, or access controls. No evidence of vulnerability fixes or security enhancements in the payload changes.
Diff
diff --git a/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.md b/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.md index c0717ea8d..1681f177c 100644 --- a//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.md +++ b//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-invoking-devops-agent-through-webhook.md @@ -95 +95 @@ When to use | Recommended when you need stronger security guarantees, such as fo - 4. In the **Webhook** section, click **Configure** + 4. In the **Webhook** section, choose **Configure** @@ -108 +108 @@ Webhooks are automatically generated when you complete the configuration of a th - 1. Click **Generate webhook** + 1. Choose **Generate webhook** @@ -125 +125 @@ Use the webhook endpoint URL and credentials to configure your external system t -**Removing credentials** – To delete webhook credentials, go to the webhook configuration section and click **Remove**. After removing credentials, the webhook endpoint will no longer accept requests until you generate new credentials. +**Removing credentials** – To delete webhook credentials, go to the webhook configuration section and choose **Remove**. After removing credentials, the webhook endpoint will no longer accept requests until you generate new credentials. @@ -166,2 +165,0 @@ The request body should include information about the incident: - json - @@ -169,3 +167,6 @@ The request body should include information about the incident: - "title": "Incident title", - "severity": "high", - "affectedResources": ["resource-id-1", "resource-id-2"], + "eventType": "incident", + "incidentId": "incident-123", + "action": "created", + "priority": "HIGH", + "title": "High CPU usage on production server", + "description": "High CPU usage on production server host ABC in AWS account 1234 region us-east-1", @@ -173 +174 @@ The request body should include information about the incident: - "description": "Detailed incident description", + "service": "MyProductionService",