AWS singlesignon documentation change
Summary
Updated references from 'AWS Directory Service' to 'Directory Service' for consistency in terminology
Security assessment
Changes involve branding/terminology updates without altering security-related content. No vulnerabilities or security features are mentioned.
Diff
diff --git a/singlesignon/latest/userguide/manage-your-identity-source-ad.md b/singlesignon/latest/userguide/manage-your-identity-source-ad.md index 949d1d036..9d02a1e61 100644 --- a//singlesignon/latest/userguide/manage-your-identity-source-ad.md +++ b//singlesignon/latest/userguide/manage-your-identity-source-ad.md @@ -11 +11 @@ With AWS IAM Identity Center, you can connect a self-managed directory in Active -AWS Directory Service helps you to set up and run a standalone AWS Managed Microsoft AD directory hosted in the AWS Cloud. You can also use AWS Directory Service to connect your AWS resources with an existing self-managed AD. To configure AWS Directory Service to work with your self-managed AD, you must first set up trust relationships to extend authentication to the cloud. +AWS Directory Service helps you to set up and run a standalone AWS Managed Microsoft AD directory hosted in the AWS Cloud. You can also use Directory Service to connect your AWS resources with an existing self-managed AD. To configure AWS Directory Service to work with your self-managed AD, you must first set up trust relationships to extend authentication to the cloud. @@ -13 +13 @@ AWS Directory Service helps you to set up and run a standalone AWS Managed Micro -IAM Identity Center uses the connection provided by AWS Directory Service to perform pass-through authentication to the source AD instance. When you use AWS Managed Microsoft AD as your identity source, IAM Identity Center can work with users from AWS Managed Microsoft AD or from any domain connected through an AD trust. If you want to locate your users in four or more domains, users must use the `DOMAIN\user` syntax as their user name when performing sign-ins to IAM Identity Center. +IAM Identity Center uses the connection provided by Directory Service to perform pass-through authentication to the source AD instance. When you use AWS Managed Microsoft AD as your identity source, IAM Identity Center can work with users from AWS Managed Microsoft AD or from any domain connected through an AD trust. If you want to locate your users in four or more domains, users must use the `DOMAIN\user` syntax as their user name when performing sign-ins to IAM Identity Center. @@ -17 +17 @@ IAM Identity Center uses the connection provided by AWS Directory Service to per - * As a prerequisite step, make sure your AD Connector or directory in AWS Managed Microsoft AD in AWS Directory Service resides within your AWS Organizations management account. + * As a prerequisite step, make sure your AD Connector or directory in AWS Managed Microsoft AD in Directory Service resides within your AWS Organizations management account. @@ -51 +51 @@ If you decide to change IAM Identity Center identity source from any other sourc -IAM Identity Center uses the connection provided by the AWS Directory Service to synchronize user, group, and membership information from your source directory in Active Directory to the IAM Identity Center identity store. No password information is synchronized to IAM Identity Center, because user authentication takes place directly from the source directory in Active Directory. This identity data is used by applications to facilitate in-app lookup, authorization, and collaboration scenarios without passing LDAP activity back to the source directory in Active Directory. +IAM Identity Center uses the connection provided by the Directory Service to synchronize user, group, and membership information from your source directory in Active Directory to the IAM Identity Center identity store. No password information is synchronized to IAM Identity Center, because user authentication takes place directly from the source directory in Active Directory. This identity data is used by applications to facilitate in-app lookup, authorization, and collaboration scenarios without passing LDAP activity back to the source directory in Active Directory.