AWS prescriptive-guidance documentation change
Summary
Updated all references from 'Quick Suite' to 'Quick' throughout the document, including headings, descriptions, and user guidance. Modified image descriptions and adjusted terminology for consistency.
Security assessment
The changes are purely cosmetic rebranding updates (changing 'Quick Suite' to 'Quick') without modifying any security policies, permissions, or access control mechanisms. No vulnerabilities, security weaknesses, or incidents are addressed. Existing security documentation links remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/quick-suite-access-approach/iam-users.md b/prescriptive-guidance/latest/quick-suite-access-approach/iam-users.md index e358c3e2c..a64c537ae 100644 --- a//prescriptive-guidance/latest/quick-suite-access-approach/iam-users.md +++ b//prescriptive-guidance/latest/quick-suite-access-approach/iam-users.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 @@ Considerations and use casesPrerequisitesConfiguring access -# Granting Quick Suite access to IAM users +# Granting Quick access to IAM users @@ -13 +13 @@ An _IAM user_ is an entity that you create in AWS Identity and Access Management - + @@ -17 +17 @@ The following are the characteristics of this architecture and access approach: - * The Amazon Quick Suite user record is linked to the user in IAM. + * The Amazon Quick user record is linked to the user in IAM. @@ -23 +23 @@ The following are the characteristics of this architecture and access approach: - * This type of user can log in through the Quick Suite console or through the AWS Management Console. + * This type of user can log in through the Quick console or through the AWS Management Console. @@ -30 +30 @@ The following are the characteristics of this architecture and access approach: -Although AWS generally doesn't recommend configuring access through IAM users, other access approaches, such as federation, might not be currently available in your organization. Many organizations that are just starting their cloud journey have not yet established IAM roles and are working in a single-account architecture. If your organization uses IAM users to access your AWS environment, then reapplying that approach to Quick Suite might be the most straightforward and sensible approach until your organization supports other approaches. +Although AWS generally doesn't recommend configuring access through IAM users, other access approaches, such as federation, might not be currently available in your organization. Many organizations that are just starting their cloud journey have not yet established IAM roles and are working in a single-account architecture. If your organization uses IAM users to access your AWS environment, then reapplying that approach to Quick might be the most straightforward and sensible approach until your organization supports other approaches. @@ -36 +36 @@ Although AWS generally doesn't recommend configuring access through IAM users, o - * Administrative permissions in Quick Suite (see IAM identity-based policies for the [Standard](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-all-access-standard-edition) or [Enterprise](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-all-access-enterprise-edition) editions) + * Administrative permissions in Quick (see IAM identity-based policies for the [Standard](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-all-access-standard-edition) or [Enterprise](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-all-access-enterprise-edition) editions) @@ -40 +40 @@ Although AWS generally doesn't recommend configuring access through IAM users, o - * For the self-provisioned access approach, the user needs permissions to create Amazon Quick Suite (see [IAM identity-based policies for Quick Suite: creating users](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-create-users)) + * For the self-provisioned access approach, the user needs permissions to create Amazon Quick (see [IAM identity-based policies for Quick: creating users](https://docs.aws.amazon.com/quicksuite/latest/userguide/iam-policy-examples.html#security_iam_id-based-policy-examples-create-users)) @@ -49 +49 @@ Although AWS generally doesn't recommend configuring access through IAM users, o -You can grant access to Quick Suite for IAM users by using either of the following options: +You can grant access to Quick for IAM users by using either of the following options: @@ -51 +51 @@ You can grant access to Quick Suite for IAM users by using either of the followi - * **Direct invitation** – You invite the IAM user to access Quick Suite, and the user can accept the invitation through their email. + * **Direct invitation** – You invite the IAM user to access Quick, and the user can accept the invitation through their email. @@ -53 +53 @@ You can grant access to Quick Suite for IAM users by using either of the followi - * **Self-provisioned access** – You create an IAM policy that permits users to provision their own access. When a user accesses Quick Suite for the first time, they are granted access and define the email address that will be associated with their Quick Suite user record. + * **Self-provisioned access** – You create an IAM policy that permits users to provision their own access. When a user accesses Quick for the first time, they are granted access and define the email address that will be associated with their Quick user record. @@ -58 +58 @@ You can grant access to Quick Suite for IAM users by using either of the followi -The result of both options is the same: the IAM user can access Quick Suite. However, there are advantages and disadvantages to each, as shown in the following table. For example, the direct invitation might be preferable for organizations that want to enforce use of approved corporate email addresses. +The result of both options is the same: the IAM user can access Quick. However, there are advantages and disadvantages to each, as shown in the following table. For example, the direct invitation might be preferable for organizations that want to enforce use of approved corporate email addresses. @@ -64 +64 @@ Direct invitation | - * Administrators can control which email address is associated with the user record in Quick Suite + * Administrators can control which email address is associated with the user record in Quick @@ -78 +78 @@ Self-provisioned access | - * Administrators can't control which email address the user provides to Quick Suite + * Administrators can't control which email address the user provides to Quick @@ -84 +84 @@ Self-provisioned access | -For instructions on how to configure access for an IAM user, see [Inviting users to access Amazon Quick Suite](https://docs.aws.amazon.com/quicksuite/latest/userguide/managing-user-access-qs-iam.html#inviting-users). Note the following when configuring this type of user access: +For instructions on how to configure access for an IAM user, see [Inviting users to access Amazon Quick](https://docs.aws.amazon.com/quicksuite/latest/userguide/managing-user-access-qs-iam.html#inviting-users). Note the following when configuring this type of user access: @@ -86 +86 @@ For instructions on how to configure access for an IAM user, see [Inviting users - * For the Quick Suite username, enter the username of the IAM user. Allowed characters are letters, numbers, and the following characters: . _ - (hyphen). + * For the Quick username, enter the username of the IAM user. Allowed characters are letters, numbers, and the following characters: . _ - (hyphen). @@ -99 +99 @@ For instructions on how to configure access for an IAM user, see [Inviting users -When IAM users can self-provision access, they don't need to be invited to the Quick Suite account. The first time they try to access the Quick Suite console, they must enter an email address. When the user chooses **Continue** , Quick Suite creates a user record for that IAM user. +When IAM users can self-provision access, they don't need to be invited to the Quick account. The first time they try to access the Quick console, they must enter an email address. When the user chooses **Continue** , Quick creates a user record for that IAM user. @@ -111 +111 @@ Active Directory users -Quick Suite users +Quick users