AWS amplify medium security documentation change
Summary
Added explanation about webhook usage for builds, changed section title to 'Security', and added content about service roles for CloudWatch Logs access
Security assessment
The change introduces security documentation by adding a section about service roles for CloudWatch Logs access and explicitly labels a 'Security' section. This relates to access control and permissions management.
Diff
diff --git a/amplify/latest/userguide/unified-webhooks.md b/amplify/latest/userguide/unified-webhooks.md index 5335ea4a4..7b718df40 100644 --- a//amplify/latest/userguide/unified-webhooks.md +++ b//amplify/latest/userguide/unified-webhooks.md @@ -9 +9 @@ Getting started with unified webhooks -The unified webhooks feature improves Amplify's integrations with Git providers and enables you to connect more Amplify applications to a single repository. With unified webhooks, Amplify now uses a single webhook per Region for all associated applications in your repository. For example, if your repository is connected to applications in both the US East (N. Virginia) and US West (Oregon) Regions, you will have two unified webhooks. +Amplify Hosting uses webhooks to automatically initiate a build after a new commit to your Git repository. The unified webhooks feature improves Amplify's integrations with Git providers and enables you to connect more Amplify applications to a single repository. With unified webhooks, Amplify now uses a single webhook per Region for all associated applications in your repository. For example, if your repository is connected to applications in both the US East (N. Virginia) and US West (Oregon) Regions, you will have two unified webhooks. @@ -61 +61 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Using webhooks +Adding a service role to access CloudWatch Logs @@ -63 +63 @@ Using webhooks -Incoming webhooks +Security