AWS prescriptive-guidance documentation change
Summary
Changed 'Amazon QuickSight' to 'Amazon Quick Suite' in title and authentication context
Security assessment
Update maintains existing security guidance about SAML 2.0 federation and IAM Identity Center without modifying security recommendations or configurations.
Diff
diff --git a/prescriptive-guidance/latest/quicksight-access-approach/federated-users.md b/prescriptive-guidance/latest/quicksight-access-approach/federated-users.md index 47711d937..b43812e60 100644 --- a//prescriptive-guidance/latest/quicksight-access-approach/federated-users.md +++ b//prescriptive-guidance/latest/quicksight-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 QuickSight](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing the right access approach for Amazon Quick Suite](introduction.html) @@ -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 QuickSight. QuickSight 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 QuickSight 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 Suite. QuickSight 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 QuickSight 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.