AWS workspaces documentation change
Summary
Updated references from 'AWS Directory Service' to 'Directory Service' and adjusted link text
Security assessment
Changes involve branding/terminology updates (removing 'AWS' prefix) and link text adjustments. No security-related content modifications.
Diff
diff --git a/workspaces/latest/adminguide/launch-workspace-microsoft-ad.md b/workspaces/latest/adminguide/launch-workspace-microsoft-ad.md index 0ff6101dd..7bcf0c16c 100644 --- a//workspaces/latest/adminguide/launch-workspace-microsoft-ad.md +++ b//workspaces/latest/adminguide/launch-workspace-microsoft-ad.md @@ -9 +9 @@ In this tutorial, we create an AWS Managed Microsoft AD directory. For tutorials -First, create an AWS Managed Microsoft AD directory. AWS Directory Service creates two directory servers, one in each of the private subnets of your VPC. Note that there are no users in the directory initially. You will add a user in the next step when you launch the WorkSpace. +First, create an AWS Managed Microsoft AD directory. Directory Service creates two directory servers, one in each of the private subnets of your VPC. Note that there are no users in the directory initially. You will add a user in the next step when you launch the WorkSpace. @@ -63 +63 @@ If you need to update your DNS server after launching your WorkSpaces, follow th -After you’ve created an AWS Managed Microsoft AD directory, you can register it with Amazon WorkSpaces. For more information, see [Register an existing AWS Directory Service directory with WorkSpaces Personal](./register-deregister-directory.html) +After you’ve created an AWS Managed Microsoft AD directory, you can register it with Amazon WorkSpaces. For more information, see [Register an existing Directory Service directory with WorkSpaces Personal](./register-deregister-directory.html)