AWS singlesignon documentation change
Summary
Updated product name references from 'Amazon QuickSight' to 'Amazon Quick Suite' and removed mention of IAM users in federation context
Security assessment
The change removes reference to IAM users in federation workflows, potentially encouraging use of more secure federation methods over direct IAM user management. However, there's no explicit mention of addressing a vulnerability or security incident. The product name change appears to be a rebranding update without security implications.
Diff
diff --git a/singlesignon/latest/userguide/what-is.md b/singlesignon/latest/userguide/what-is.md index e5fa5826d..21572b54c 100644 --- a//singlesignon/latest/userguide/what-is.md +++ b//singlesignon/latest/userguide/what-is.md @@ -9 +9 @@ Why use IAM Identity Center?IAM Identity Center rename -AWS IAM Identity Center is the AWS solution for connecting your workforce users to AWS managed applications such as Amazon Q Developer and Amazon QuickSight, and other AWS resources. You can connect your existing identity provider and synchronize users and groups from your directory, or create and manage your users directly in IAM Identity Center. You can then use IAM Identity Center for either or both of the following: +AWS IAM Identity Center is the AWS solution for connecting your workforce users to AWS managed applications such as Amazon Q Developer and Amazon Quick Suite, and other AWS resources. You can connect your existing identity provider and synchronize users and groups from your directory, or create and manage your users directly in IAM Identity Center. You can then use IAM Identity Center for either or both of the following: @@ -20 +20 @@ AWS IAM Identity Center is the AWS solution for connecting your workforce users -You don’t need to make any changes to your current AWS account workflows to use IAM Identity Center for access to AWS managed applications. If you’re using [federation with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers.html#id_roles_providers_iam) or IAM users for AWS account access, your users can continue to access AWS accounts in the same way they always have, and you can continue to use your existing workflows to manage that access. +You don’t need to make any changes to your current AWS account workflows to use IAM Identity Center for access to AWS managed applications. If you’re using [federation with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers.html#id_roles_providers_iam) for AWS account access, your users can continue to access AWS accounts in the same way they always have, and you can continue to use your existing workflows to manage that access. @@ -38 +38 @@ Trusted identity propagation across applications** -With trusted identity propagation, AWS managed applications such as Amazon QuickSight can securely share a user’s identity with other AWS managed applications such as Amazon Redshift and authorize access to AWS resources based on the user’s identity. You can more easily audit user activity because CloudTrail events are logged based on the user and the actions the user initiated. This makes it easier to understand who accessed what. For information about supported use cases, including end-to-end configuration guidance, see [Trusted identity propagation use cases](./trustedidentitypropagation-integrations.html). +With trusted identity propagation, AWS managed applications such as Amazon Quick Suite can securely share a user’s identity with other AWS managed applications such as Amazon Redshift and authorize access to AWS resources based on the user’s identity. You can more easily audit user activity because CloudTrail events are logged based on the user and the actions the user initiated. This makes it easier to understand who accessed what. For information about supported use cases, including end-to-end configuration guidance, see [Trusted identity propagation use cases](./trustedidentitypropagation-integrations.html).