AWS quick documentation change
Summary
Restructured permissions documentation with simplified headers and consolidated security controls into bullet points. Removed detailed explanations of approval workflows and Bedrock model governance, replaced with simplified feature toggles.
Security assessment
The changes document existing security controls (permissions management, sharing approvals, model usage restrictions) but do not address a specific vulnerability. While security features are described more concisely, there's no evidence of patching a vulnerability or incident response.
Diff
diff --git a/quick/latest/userguide/managing-quick-flows-permissions-and-assets.md b/quick/latest/userguide/managing-quick-flows-permissions-and-assets.md index 09f9471a3..1f70e07df 100644 --- a//quick/latest/userguide/managing-quick-flows-permissions-and-assets.md +++ b//quick/latest/userguide/managing-quick-flows-permissions-and-assets.md @@ -5 +5 @@ -Using Custom Permissions pageUsing Asset Management page +Custom Permissions pageAsset Management page @@ -9 +9 @@ Using Custom Permissions pageUsing Asset Management page -Administrative control over Quick Flows permissions and assets is managed through two primary interfaces in the Amazon Quick console: the Custom Permissions page for controlling capabilities and features, and the Asset Management page for overseeing Flow sharing and ownership. These tools provide comprehensive governance over how Quick Flows operates within your organization. +Administrators manage Quick Flows permissions and assets through two interfaces in the Quick console: the Custom Permissions page and the Asset Management page. @@ -11 +11 @@ Administrative control over Quick Flows permissions and assets is managed throug -## Using Custom Permissions page +## Custom Permissions page @@ -13 +13 @@ Administrative control over Quick Flows permissions and assets is managed throug -The Custom Permissions page provides centralized control over Quick Flows capabilities and features available to users in your account. Through this interface, you can enable or disable core functionality and manage approval workflows that govern how flows are shared within your organization. +The Custom Permissions page controls which Quick Flows capabilities and features are available to users. @@ -17 +17 @@ The Custom Permissions page provides centralized control over Quick Flows capabi -The restrict capabilities section allows you to control fundamental Quick Flows functionality at the account level. This provides a master switch for Quick Flows availability across your entire organization. + * **Enable or disable flows** — Control whether Quick Flows is available to users in your account. When disabled, all Quick Flows functionality is unavailable, but existing flows are preserved. Quick Flows is enabled by default for new Quick instances. @@ -19 +18,0 @@ The restrict capabilities section allows you to control fundamental Quick Flows -#### Enable or disable flows for all users @@ -21 +19,0 @@ The restrict capabilities section allows you to control fundamental Quick Flows -Administrators can enable or disable Quick Flows access for all users in the account through a single control. This setting affects both the creation and usage of flows across your organization. @@ -23,3 +20,0 @@ Administrators can enable or disable Quick Flows access for all users in the acc -When Quick Flows is enabled, users with appropriate permissions can create, edit, share, and run flows according to their assigned roles. When disabled, all Quick Flows functionality becomes unavailable to users, though existing flows remain preserved and can be re-enabled later. - -By default, Quick Flows is enabled for new Amazon Quick instances and for existing Amazon Quick Sight instances that upgrade to the Amazon Quick experience. This opt-out approach ensures that organizations can immediately begin using Quick Flows capabilities while providing administrators the flexibility to disable the feature if needed for governance or compliance reasons. @@ -29,17 +24 @@ By default, Quick Flows is enabled for new Amazon Quick instances and for existi -The restrict features section provides granular control over specific Quick Flows capabilities, allowing administrators to selectively enable or disable advanced features based on organizational requirements. - -#### Enable or disable approval review - -Administrators can enable or disable approval review for Quick Flows sharing within the organization. When approval review is enabled, any flow that needs to be shared with users, groups, or made available to all users requires administrative approval before becoming accessible. - -The approval review setting is disabled by default, allowing flow creators to share their work immediately upon creation. When you enable approval review, the system implements a review process where administrators must explicitly approve each flow before it becomes available to the intended audience. - -This feature is particularly valuable for organizations that require content review and approval processes, ensuring that all shared flows meet organizational standards and compliance requirements before reaching end users. - -#### Enable or disable Amazon Bedrock model usage for General knowledge step in flows - -Administrators can control whether Amazon Bedrock models are available for use in General knowledge steps within Flows. This setting provides organizational control over AI model usage in Flow workflows. - -By default, Amazon Bedrock model usage is enabled for General knowledge steps in flows. Administrators can disable this capability to prevent flow creators from using Bedrock models in their General knowledge steps, ensuring alignment with organizational policies or compliance requirements. - -When Bedrock model usage is disabled, flow creators will not be able to configure General knowledge steps for output refinement or generate images that rely on Amazon Bedrock models. Existing flows with General knowledge steps using Bedrock models may be affected and should be reviewed by their creators. + * **Allow creators to share without approval** — When enabled, creators can share flows without review. When disabled, all eligible users can review and approve flow sharing requests. @@ -47 +26 @@ When Bedrock model usage is disabled, flow creators will not be able to configur -#### Enable or disable use of UI agent in flows + * **Enable bedrock model usage in General knowledge step for output refinement** — Controls whether Bedrock models are available for General knowledge steps. Enabled by default. @@ -49 +28 @@ When Bedrock model usage is disabled, flow creators will not be able to configur -Admins can enable UI agents to perform browser tasks in flows. + * **Enable UI agent to perform browser tasks** (Preview) — Controls whether UI agent steps can be used in flows. @@ -51 +29,0 @@ Admins can enable UI agents to perform browser tasks in flows. -## Using Asset Management page @@ -53 +30,0 @@ Admins can enable UI agents to perform browser tasks in flows. -The Asset Management page provides comprehensive oversight of all flows within your organization, enabling administrators to manage Flow sharing, ownership, and visibility. This centralized interface allows you to maintain governance over your organization's flow ecosystem. @@ -55 +31,0 @@ The Asset Management page provides comprehensive oversight of all flows within y -### Ability to share flows @@ -57 +33 @@ The Asset Management page provides comprehensive oversight of all flows within y -Through the Asset Management page, administrators can directly share flows with users or groups. This capability provides administrative oversight of flow distribution and ensures that valuable workflows reach their intended audiences. +## Asset Management page @@ -59 +35 @@ Through the Asset Management page, administrators can directly share flows with -Administrative sharing capabilities include the ability to share Flows on behalf of their creators, redistribute Flows to different user groups, and manage sharing permissions for Flows across the organization. This is particularly useful for managing orphaned Flows or redistributing workflows when team structures change. +The Asset Management page provides oversight of all flows in your organization. @@ -61 +37 @@ Administrative sharing capabilities include the ability to share Flows on behalf -Administrators can also transfer ownership of flows between users, ensuring continuity when flow creators leave the organization or when workflows need to be reassigned to different teams or departments. + * **Share flows** — Share flows on behalf of creators, redistribute flows to different groups, or manage sharing permissions across the organization. @@ -63 +39 @@ Administrators can also transfer ownership of flows between users, ensuring cont -### Ability to unlist flows from viewers + * **Transfer ownership** — Transfer flow ownership between users, such as when a creator leaves the organization. @@ -65 +41 @@ Administrators can also transfer ownership of flows between users, ensuring cont -Administrators have the authority to unlist or remove Flows from the shared library, making them unavailable to viewers while preserving the underlying Flow for potential future use. This capability is essential for maintaining quality control and governance over shared content. + * **Unlist flows** — Remove flows from the shared library, making them unavailable to viewers while preserving them for the creator to edit. Unlisted flows can be re-shared once issues are resolved. @@ -67 +42,0 @@ Administrators have the authority to unlist or remove Flows from the shared libr -The unlisting capability allows administrators to quickly respond to issues with shared Flows, such as content that doesn't meet organizational standards, contains outdated information, or requires updates before continued use. Unlisted Flows remain accessible to their creators for editing and can be re-shared once any issues are resolved. @@ -69 +43,0 @@ The unlisting capability allows administrators to quickly respond to issues with -This feature supports organizational governance by providing administrators with the ability to curate the shared Flow library, ensuring that only approved, high-quality workflows remain visible to end users while maintaining the flexibility to restore access when appropriate. @@ -71 +44,0 @@ This feature supports organizational governance by providing administrators with -When unlisting flows, administrators can view comprehensive details including the flow name, description, creation time, and creator information.