AWS prescriptive-guidance documentation change
Summary
Updated product name from 'Quick Suite' to 'Quick' throughout the document, including title changes and feature references.
Security assessment
The changes are purely cosmetic rebranding updates without altering security functionality. The email synchronization feature behavior remains identical - it still enforces email consistency through IdP integration without introducing new security controls or addressing vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/quick-suite-access-approach/email-synchronization-federated-users.md b/prescriptive-guidance/latest/quick-suite-access-approach/email-synchronization-federated-users.md index 4b3aae532..bb1479fe2 100644 --- a//prescriptive-guidance/latest/quick-suite-access-approach/email-synchronization-federated-users.md +++ b//prescriptive-guidance/latest/quick-suite-access-approach/email-synchronization-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 @@ -# Quick Suite email synchronization for federated users +# Quick email synchronization for federated users @@ -9 +9 @@ -This feature is available only for the Enterprise edition of Amazon Quick Suite. +This feature is available only for the Enterprise edition of Amazon Quick. @@ -11 +11 @@ This feature is available only for the Enterprise edition of Amazon Quick Suite. -When IAM users self-provision access to Quick Suite, administrators can't control which email address the user provides to Quick Suite. Users could enter a personal email address instead of their work email address. This might not be acceptable for some organizations. However, when you're using an identity provider to provide federated access to Quick Suite Enterprise edition, Quick Suite has a feature that ensures the user's email address in Quick Suite matches the user's email address in the identity provider. +When IAM users self-provision access to Quick, administrators can't control which email address the user provides to Quick. Users could enter a personal email address instead of their work email address. This might not be acceptable for some organizations. However, when you're using an identity provider to provide federated access to Quick Enterprise edition, Quick has a feature that ensures the user's email address in Quick matches the user's email address in the identity provider. @@ -13 +13 @@ When IAM users self-provision access to Quick Suite, administrators can't contro -In the IdP, you add a SAML attribute for the user's email address. The process for creating the attribute or token differs for each IdP. See the instructions for [Okta](https://www.okta.com/blog/2019/11/okta-and-aws-partner-to-simplify-access-via-session-tags/) or [IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/configure-abac.html), or see the documentation for your organization's IdP. The IdP passes the user's email as an IAM `Principal` session tag. Quick Suite uses this session tag instead of prompting the user to provide their email address. For instructions about how to enable this feature, see [Configuring email syncing for federated users](https://docs.aws.amazon.com/quicksuite/latest/userguide/jit-email-syncing.html) in the Quick Suite documentation. +In the IdP, you add a SAML attribute for the user's email address. The process for creating the attribute or token differs for each IdP. See the instructions for [Okta](https://www.okta.com/blog/2019/11/okta-and-aws-partner-to-simplify-access-via-session-tags/) or [IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/configure-abac.html), or see the documentation for your organization's IdP. The IdP passes the user's email as an IAM `Principal` session tag. Quick uses this session tag instead of prompting the user to provide their email address. For instructions about how to enable this feature, see [Configuring email syncing for federated users](https://docs.aws.amazon.com/quicksuite/latest/userguide/jit-email-syncing.html) in the Quick documentation.