AWS prescriptive-guidance documentation change
Summary
Updated service name references from 'Quick Suite' to 'Quick' throughout documentation, including titles, descriptions, prerequisites, and configuration steps. Modified image alt texts and links to reflect the new naming convention.
Security assessment
The changes are purely cosmetic updates to reflect a product name change ('Quick Suite' → 'Quick'). No security vulnerabilities, configurations, or features were modified. The core security mechanisms (SAML federation, IAM roles, permission sets) remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/quick-suite-access-approach/iam-identity-center-federation.md b/prescriptive-guidance/latest/quick-suite-access-approach/iam-identity-center-federation.md index 267b75b69..97616cbd0 100644 --- a//prescriptive-guidance/latest/quick-suite-access-approach/iam-identity-center-federation.md +++ b//prescriptive-guidance/latest/quick-suite-access-approach/iam-identity-center-federation.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing the right access approach for Amazon Quick Suite](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing the right access approach for Amazon Quick](introduction.html) @@ -7 +7 @@ Configuring permissions by using permission setsConfiguring permissions by using -# Configuring federated user access to Quick Suite through IAM Identity Center +# Configuring federated user access to Quick through IAM Identity Center @@ -11 +11 @@ If your enterprise is already using AWS IAM Identity Center, you might want to u -When using SAML 2.0 federation with IAM Identity Center, there are two methods to configure federated user access to Quick Suite: +When using SAML 2.0 federation with IAM Identity Center, there are two methods to configure federated user access to Quick: @@ -13 +13 @@ When using SAML 2.0 federation with IAM Identity Center, there are two methods t - * Configuring permissions by using permission sets – You can use this approach only if the AWS accounts for IAM Identity Center and Quick Suite are members of same organization in AWS Organizations. A [permission set](https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetsconcept.html) is a template that defines a collection of one or more AWS Identity and Access Management (IAM) policies. Permission sets can simplify permissions management in your organization. + * Configuring permissions by using permission sets – You can use this approach only if the AWS accounts for IAM Identity Center and Quick are members of same organization in AWS Organizations. A [permission set](https://docs.aws.amazon.com/singlesignon/latest/userguide/permissionsetsconcept.html) is a template that defines a collection of one or more AWS Identity and Access Management (IAM) policies. Permission sets can simplify permissions management in your organization. @@ -15 +15 @@ When using SAML 2.0 federation with IAM Identity Center, there are two methods t - * Configuring permissions by using IAM roles – This approach is well suited if the AWS account for Quick Suite is not part of the same organization as IAM Identity Center. In this approach, you create the IAM roles directly in the same account with Quick Suite. + * Configuring permissions by using IAM roles – This approach is well suited if the AWS account for Quick is not part of the same organization as IAM Identity Center. In this approach, you create the IAM roles directly in the same account with Quick. @@ -20 +20 @@ When using SAML 2.0 federation with IAM Identity Center, there are two methods t -In both of these approaches, users can self-provision their own Quick Suite access. If email synchronization is disabled, users can provide their preferred email address when they sign into Quick Suite. If email synchronization is enabled, Quick Suite uses the email address defined in the enterprise IdP. For more information, see [Quick Suite email synchronization for federated users](./email-synchronization-federated-users.html) in this guide. +In both of these approaches, users can self-provision their own Quick access. If email synchronization is disabled, users can provide their preferred email address when they sign into Quick. If email synchronization is enabled, Quick uses the email address defined in the enterprise IdP. For more information, see [Quick email synchronization for federated users](./email-synchronization-federated-users.html) in this guide. @@ -24 +24 @@ In both of these approaches, users can self-provision their own Quick Suite acce - + @@ -28 +28 @@ The following are the characteristics of this architecture and access approach: - 1. The AWS accounts for IAM Identity Center and Quick Suite are in the same organization in AWS Organizations. + 1. The AWS accounts for IAM Identity Center and Quick are in the same organization in AWS Organizations. @@ -34 +34 @@ The following are the characteristics of this architecture and access approach: - 4. The Quick Suite user record is linked to the IAM role managed by IAM Identity Center and the username, such as `AWSReservedSSO_QuickSightReader_7oe58cd620501f23/[email protected]`. + 4. The Quick user record is linked to the IAM role managed by IAM Identity Center and the username, such as `AWSReservedSSO_QuickSightReader_7oe58cd620501f23/[email protected]`. @@ -41 +41 @@ The following are the characteristics of this architecture and access approach: - * An active Quick Suite account + * An active Quick account @@ -45 +45 @@ The following are the characteristics of this architecture and access approach: - * Administrator access to the AWS account where Quick Suite is subscribed + * Administrator access to the AWS account where Quick is subscribed @@ -54 +54 @@ The following are the characteristics of this architecture and access approach: -Before subscribing to Quick Suite, make sure that you have already set up and configured IAM Identity Center. For instructions, see [Enabling AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/get-set-up-for-idc.html) and [Getting started tutorials](https://docs.aws.amazon.com/singlesignon/latest/userguide/tutorials.html) in the IAM Identity Center documentation. After you have configured IAM Identity Center in your organization, create a custom permission set in IAM Identity Center that allows federated users to access Quick Suite. For instructions, see [Create a permission set](https://docs.aws.amazon.com/singlesignon/latest/userguide/howtocreatepermissionset.html) in the IAM Identity Center documentation. For more information about configuring the policies that you include in the permission set, see [Configuring IAM policies](./configuring-iam-policies.html) in this guide. +Before subscribing to Quick, make sure that you have already set up and configured IAM Identity Center. For instructions, see [Enabling AWS IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/get-set-up-for-idc.html) and [Getting started tutorials](https://docs.aws.amazon.com/singlesignon/latest/userguide/tutorials.html) in the IAM Identity Center documentation. After you have configured IAM Identity Center in your organization, create a custom permission set in IAM Identity Center that allows federated users to access Quick. For instructions, see [Create a permission set](https://docs.aws.amazon.com/singlesignon/latest/userguide/howtocreatepermissionset.html) in the IAM Identity Center documentation. For more information about configuring the policies that you include in the permission set, see [Configuring IAM policies](./configuring-iam-policies.html) in this guide. @@ -56 +56 @@ Before subscribing to Quick Suite, make sure that you have already set up and co -After you create the permission set, provision it to the target AWS account where Quick Suite is subscribed, and then apply it to the users and groups who require Quick Suite access. For more information about assigning permission sets, see [Assign user access to AWS accounts](https://docs.aws.amazon.com/singlesignon/latest/userguide/useraccess.html#assignusers) in the IAM Identity Center documentation. +After you create the permission set, provision it to the target AWS account where Quick is subscribed, and then apply it to the users and groups who require Quick access. For more information about assigning permission sets, see [Assign user access to AWS accounts](https://docs.aws.amazon.com/singlesignon/latest/userguide/useraccess.html#assignusers) in the IAM Identity Center documentation. @@ -60 +60 @@ After you create the permission set, provision it to the target AWS account wher - + @@ -64 +64 @@ The following are the characteristics of this architecture and access approach: - 1. The AWS accounts for IAM Identity Center and Quick Suite are not in the same organization in AWS Organizations. + 1. The AWS accounts for IAM Identity Center and Quick are not in the same organization in AWS Organizations. @@ -70 +70 @@ The following are the characteristics of this architecture and access approach: - 4. The Quick Suite user record is linked to an IAM role and the username in the IdP, such as `QuickSightReader/[email protected]`. + 4. The Quick user record is linked to an IAM role and the username in the IdP, such as `QuickSightReader/[email protected]`. @@ -77 +77 @@ The following are the characteristics of this architecture and access approach: - * An active Quick Suite account. + * An active Quick account. @@ -81 +81 @@ The following are the characteristics of this architecture and access approach: - * Administrator access to the AWS account where Quick Suite is subscribed. + * Administrator access to the AWS account where Quick is subscribed. @@ -94 +94 @@ The following are the characteristics of this architecture and access approach: -For instructions, see the [AWS IAM Identity Center Integration Guide for Amazon Quick Suite](https://static.global.sso.amazonaws.com/app-b1262cec5a6d8194/instructions/index.htm). After you have configured IAM Identity Center as a trusted identity provider for the AWS account, create an IAM role that federated users can assume in order to access Quick Suite. For instructions, see [Creating IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the IAM documentation. For more information about configuring the policies for Quick Suite, see [Configuring IAM policies](./configuring-iam-policies.html) in this guide. +For instructions, see the [AWS IAM Identity Center Integration Guide for Amazon Quick](https://static.global.sso.amazonaws.com/app-b1262cec5a6d8194/instructions/index.htm). After you have configured IAM Identity Center as a trusted identity provider for the AWS account, create an IAM role that federated users can assume in order to access Quick. For instructions, see [Creating IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the IAM documentation. For more information about configuring the policies for Quick, see [Configuring IAM policies](./configuring-iam-policies.html) in this guide.