AWS prescriptive-guidance documentation change
Summary
Updated product references from 'Quick Suite' to 'Quick' throughout the document, including title changes and content adjustments. No technical or procedural changes were made to the federated access approach.
Security assessment
The changes are purely cosmetic, involving product name standardization from 'Quick Suite' to 'Quick'. The security content about federated access using SAML 2.0, temporary credentials, and IAM roles remains unchanged. There's no evidence of security vulnerability fixes or new security features.
Diff
diff --git a/prescriptive-guidance/latest/quick-suite-access-approach/federated-users.md b/prescriptive-guidance/latest/quick-suite-access-approach/federated-users.md index 508fbd9e3..871aa44f8 100644 --- a//prescriptive-guidance/latest/quick-suite-access-approach/federated-users.md +++ b//prescriptive-guidance/latest/quick-suite-access-approach/federated-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) @@ -5 +5 @@ -# Granting Quick Suite access to federated users +# Granting Quick access to federated users @@ -7 +7 @@ -When you use federated identities, you can manage users with an external identity provider (IdP) to authenticate users when they sign in to Amazon Quick Suite. Quick Suite supports identity federation with SAML 2.0. Many external IdPs, such as Okta and Ping, use this standard. You can also use AWS IAM Identity Center as your external IdP for a SAML 2.0 federation approach to Quick Suite access. However, we recommend the built-in service integration discussed in [IAM Identity Center integration](./iam-identity-center-integration.html) in this guide instead of the federated user approach. If you use IAM Identity Center, the federated user approach is only recommended if you cannot use IAM Identity Center integration due to current feature limitations. +When you use federated identities, you can manage users with an external identity provider (IdP) to authenticate users when they sign in to Amazon Quick. Quick supports identity federation with SAML 2.0. Many external IdPs, such as Okta and Ping, use this standard. You can also use AWS IAM Identity Center as your external IdP for a SAML 2.0 federation approach to Quick access. However, we recommend the built-in service integration discussed in [IAM Identity Center integration](./iam-identity-center-integration.html) in this guide instead of the federated user approach. If you use IAM Identity Center, the federated user approach is only recommended if you cannot use IAM Identity Center integration due to current feature limitations. @@ -9 +9 @@ When you use federated identities, you can manage users with an external identit -Federated users have a single sign-on (SSO) experience, and you can grant access to Quick Suite without creating an AWS Identity and Access Management (IAM) user or Quick Suite local user for each person in your organization. In addition, federation provides users with temporary credentials, which is a [security best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp). For more information about identity federation and its benefits and use cases, see [Identity federation in AWS](https://aws.amazon.com/identity/federation/). +Federated users have a single sign-on (SSO) experience, and you can grant access to Quick without creating an AWS Identity and Access Management (IAM) user or Quick local user for each person in your organization. In addition, federation provides users with temporary credentials, which is a [security best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp). For more information about identity federation and its benefits and use cases, see [Identity federation in AWS](https://aws.amazon.com/identity/federation/). @@ -11 +11 @@ Federated users have a single sign-on (SSO) experience, and you can grant access -When configuring access to Quick Suite for federated users, you can use one of the following approaches: +When configuring access to Quick for federated users, you can use one of the following approaches: @@ -13 +13 @@ When configuring access to Quick Suite for federated users, you can use one of t - * [Configuring federated user access to Quick Suite through IAM and an external IdP](./external-idp.html) + * [Configuring federated user access to Quick through IAM and an external IdP](./external-idp.html) @@ -15 +15 @@ When configuring access to Quick Suite for federated users, you can use one of t - * [Configuring federated user access to Quick Suite through IAM Identity Center](./iam-identity-center-federation.html) + * [Configuring federated user access to Quick through IAM Identity Center](./iam-identity-center-federation.html) @@ -20 +20 @@ When configuring access to Quick Suite for federated users, you can use one of t -Both of these approaches allow federated users to self-provision access to Quick Suite. The approaches vary based on the architecture and services used for federation. However, in both solutions, the federated user then assumes an IAM role that determines which permissions they have in Quick Suite. +Both of these approaches allow federated users to self-provision access to Quick. The approaches vary based on the architecture and services used for federation. However, in both solutions, the federated user then assumes an IAM role that determines which permissions they have in Quick. @@ -22 +22 @@ Both of these approaches allow federated users to self-provision access to Quick -When you use Quick Suite Enterprise edition, you can force users who are self-provisioning their access to sign in to Quick Suite by using the email address defined in the identity provider. For more information, see [Quick Suite email synchronization for federated users](./email-synchronization-federated-users.html). +When you use Quick Enterprise edition, you can force users who are self-provisioning their access to sign in to Quick by using the email address defined in the identity provider. For more information, see [Quick email synchronization for federated users](./email-synchronization-federated-users.html).