AWS quicksuite medium security documentation change
Summary
Updated integration setup instructions to require adding integrations to Automation Groups for access control, replacing previous integration configuration guidance.
Security assessment
The change introduces mandatory Automation Group association for integrations, implementing access control boundaries. This prevents unauthorized automations from accessing integrations by enforcing group-based permissions, addressing potential privilege escalation risks.
Diff
diff --git a/quicksuite/latest/userguide/getting-started-quick-automate.md b/quicksuite/latest/userguide/getting-started-quick-automate.md index c8e4e726b..0f4f0e858 100644 --- a//quicksuite/latest/userguide/getting-started-quick-automate.md +++ b//quicksuite/latest/userguide/getting-started-quick-automate.md @@ -66 +66 @@ Amazon Quick Automate provides granular role based access: Viewer, Contributor, -If your automation interacts with external applications such as Salesforce or Jira via APIs, make sure all necessary integrations are configured. For more information, see [Action connectors](./action-integrations.html). + * After setting up AWS service integrations, you can begin using them in Quick Automate. See [Action connectors](./action-integrations.html) for setup details. @@ -68 +68 @@ If your automation interacts with external applications such as Salesforce or Ji - * Navigate to **Connections → Integrations** in the left panel to create new integrations. + * First, add the integration to an Automation Group. This allows you to control access for which automations can use this integration. To add an integration to your Automation Group: @@ -70 +70 @@ If your automation interacts with external applications such as Salesforce or Ji - * Currently, only integrations available under the **Actions** tab are supported in Amazon Quick Automate. + * Go to the **Projects** page @@ -72 +72 @@ If your automation interacts with external applications such as Salesforce or Ji - * Once an integration is created, associate it with the **Automation Group** where it will be used. + * Click **Manage groups** and select the group you want to add an integration to @@ -74 +74,5 @@ If your automation interacts with external applications such as Salesforce or Ji - * The associated actions will then appear in the canvas. During deployment, you can select the appropriate connection to be used by the deployed automation. + * In the **Assets** sections, click **Add** , and then **Actions** + + * Select the Integration you created earlier and click **Add** to link it to your Automation Group + + * Now when users create projects in that Automation Group, they will find the actions associated with this Integration and be able to select this Integration for authentication