AWS prescriptive-guidance documentation change
Summary
Updated product name references from 'Amazon Quick Suite' to 'Amazon Quick' in two places.
Security assessment
The change involves minor product name corrections without any security context. No vulnerabilities, security configurations, or access control changes are mentioned. The authentication/authorization workflow remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/security-reference-architecture-identity-management/workforce-iam-identity-center.md b/prescriptive-guidance/latest/security-reference-architecture-identity-management/workforce-iam-identity-center.md index c15ab846b..50e42a929 100644 --- a//prescriptive-guidance/latest/security-reference-architecture-identity-management/workforce-iam-identity-center.md +++ b//prescriptive-guidance/latest/security-reference-architecture-identity-management/workforce-iam-identity-center.md @@ -11 +11 @@ Connecting your existing identity source to IAM Identity CenterCreating and mana -AWS managed services, including Amazon Q, Amazon Q Developer, Amazon SageMaker Studio, and Amazon Quick Suite, integrate and use IAM Identity Center for authentication and authorization. You connect your identity source only once to IAM Identity Center and manage workforce access to all onboarded [AWS-managed applications](https://docs.aws.amazon.com/singlesignon/latest/userguide/awsapps.html). Identities from your existing corporate directories, such as Microsoft Entra ID, Okta, Google Workspace, and Microsoft Active Directory, must be provisioned into IAM Identity Center before you can look up users or groups to grant them single sign-on access to AWS managed services. IAM Identity Center also powers application-specific, user-centric experiences. For example, users of Amazon Q experience continuity as they move from one Amazon Q-integrated service to another. +AWS managed services, including Amazon Q, Amazon Q Developer, Amazon SageMaker Studio, and Amazon Quick, integrate and use IAM Identity Center for authentication and authorization. You connect your identity source only once to IAM Identity Center and manage workforce access to all onboarded [AWS-managed applications](https://docs.aws.amazon.com/singlesignon/latest/userguide/awsapps.html). Identities from your existing corporate directories, such as Microsoft Entra ID, Okta, Google Workspace, and Microsoft Active Directory, must be provisioned into IAM Identity Center before you can look up users or groups to grant them single sign-on access to AWS managed services. IAM Identity Center also powers application-specific, user-centric experiences. For example, users of Amazon Q experience continuity as they move from one Amazon Q-integrated service to another. @@ -19 +19 @@ You can use IAM Identity Center capabilities individually. For example, you migh -AWS managed services that integrate with trusted identity propagation, such as Amazon Redshift query editor v2, Amazon EMR, and Amazon Quick Suite, obtain tokens from IAM Identity Center directly. IAM Identity Center also provides an option for applications to exchange identity tokens and access tokens from an external OAuth 2.0 authorization server. User access to AWS services and other events is recorded in service-specific logs and in AWS CloudTrail events, so auditors know what actions the users took and which resources they accessed. +AWS managed services that integrate with trusted identity propagation, such as Amazon Redshift query editor v2, Amazon EMR, and Amazon Quick, obtain tokens from IAM Identity Center directly. IAM Identity Center also provides an option for applications to exchange identity tokens and access tokens from an external OAuth 2.0 authorization server. User access to AWS services and other events is recorded in service-specific logs and in AWS CloudTrail events, so auditors know what actions the users took and which resources they accessed.