AWS devopsagent documentation change
Summary
Updated PagerDuty integration steps: replaced 'click' with 'choose' in UI instructions and expanded required OAuth scopes to include webhook_subscriptions permissions
Security assessment
The added webhook_subscriptions.read/write permissions enhance security by explicitly requiring least-privilege access for webhook management. No evidence of vulnerability remediation, but improves security posture through refined permissions documentation.
Diff
diff --git a/devopsagent/latest/userguide/connecting-to-ticketing-and-chat-connecting-pagerduty.md b/devopsagent/latest/userguide/connecting-to-ticketing-and-chat-connecting-pagerduty.md index 2bb0dd067..0b2fe8748 100644 --- a//devopsagent/latest/userguide/connecting-to-ticketing-and-chat-connecting-pagerduty.md +++ b//devopsagent/latest/userguide/connecting-to-ticketing-and-chat-connecting-pagerduty.md @@ -40 +40 @@ PagerDuty is registered at the AWS account level and shared among all Agent Spac - 4. Find **PagerDuty** in the **Available** providers section under **Communication** and click **Register** + 4. Find **PagerDuty** in the **Available** providers section under **Communication** and choose **Register** @@ -60 +60 @@ PagerDuty is registered at the AWS account level and shared among all Agent Spac - * Under **Permissions** , grant the following minimum required scopes: `incidents.read`, `incidents.write`, and `services.read` + * Under **Permissions** , grant the following minimum required scopes: `incidents.read`, `incidents.write`, `services.read`, `webhook_subscriptions.read`, and `webhook_subscriptions.write` @@ -69 +69 @@ PagerDuty is registered at the AWS account level and shared among all Agent Spac - * **Permission scope** – The minimum required scopes are: `incidents.read`, `incidents.write`, `services.read` + * **Permission scope** – The minimum required scopes are: `incidents.read`, `incidents.write`, `services.read`, `webhook_subscriptions.read`, `webhook_subscriptions.write` @@ -84 +84 @@ PagerDuty is registered at the AWS account level and shared among all Agent Spac - 2. Click **Submit** to complete the registration + 2. Choose **Submit** to complete the registration @@ -99 +99 @@ After registering PagerDuty at the account level, you can connect it to individu - 3. In the **Communications** section, click **Add** + 3. In the **Communications** section, choose **Add** @@ -103 +103 @@ After registering PagerDuty at the account level, you can connect it to individu - 5. Click **Save** + 5. Choose **Save** @@ -114 +114 @@ After registering PagerDuty at the account level, you can connect it to individu - * **Removing PagerDuty** – To disconnect PagerDuty from an Agent Space, select it in the Communications section and click **Remove**. To completely remove the registration, remove it from all Agent Spaces first, then deregister from the Capability Providers page. + * **Removing PagerDuty** – To disconnect PagerDuty from an Agent Space, select it in the Communications section and choose **Remove**. To completely remove the registration, remove it from all Agent Spaces first, then deregister from the Capability Providers page.