AWS directoryservice documentation change
Summary
Updated references from 'AWS Directory Service' to 'Directory Service' throughout the document for consistency
Security assessment
The changes are purely branding/terminology updates (removing 'AWS' prefix from service name references). No security vulnerabilities, mitigations, or new security features are introduced. Existing security recommendations (like using minimal privilege service accounts) remain unchanged.
Diff
diff --git a/directoryservice/latest/admin-guide/ad_connector_getting_started.md b/directoryservice/latest/admin-guide/ad_connector_getting_started.md index 924af662b..4166a764c 100644 --- a//directoryservice/latest/admin-guide/ad_connector_getting_started.md +++ b//directoryservice/latest/admin-guide/ad_connector_getting_started.md @@ -9 +9 @@ AD Connector prerequisitesCreate an AD Connector -With AD Connector you can connect AWS Directory Service to your existing enterprise Active Directory. When connected to your existing directory, all of your directory data remains on your domain controllers. AWS Directory Service does not replicate any of your directory data. +With AD Connector you can connect Directory Service to your existing enterprise Active Directory. When connected to your existing directory, all of your directory data remains on your domain controllers. Directory Service does not replicate any of your directory data. @@ -42 +42 @@ You can use IPv6 for your VPC. For more information, see [IPv6 support for your -AWS Directory Service uses a two VPC structure. The EC2 instances which make up your directory run outside of your AWS account, and are managed by AWS. They have two network adapters, `ETH0` and `ETH1`. `ETH0` is the management adapter, and exists outside of your account. `ETH1` is created within your account. +Directory Service uses a two VPC structure. The EC2 instances which make up your directory run outside of your AWS account, and are managed by AWS. They have two network adapters, `ETH0` and `ETH1`. `ETH0` is the management adapter, and exists outside of your account. `ETH1` is created within your account. @@ -214 +214 @@ To support multi-factor authentication with your AD Connector directory, you nee - * To create the endpoints, you need the IP addresses of the AWS Directory Service servers. These IP addresses can be obtained from the **Directory IP Address** field of your directory details. + * To create the endpoints, you need the IP addresses of the Directory Service servers. These IP addresses can be obtained from the **Directory IP Address** field of your directory details. @@ -218 +218 @@ To support multi-factor authentication with your AD Connector directory, you nee - * Your existing network must allow inbound traffic over the default RADIUS server port (1812) from the AWS Directory Service servers. + * Your existing network must allow inbound traffic over the default RADIUS server port (1812) from the Directory Service servers. @@ -229 +229 @@ For more information about using AD Connector with MFA, see [Enabling multi-fact -To connect to your existing directory, you must have the credentials for your AD Connector service account in the existing directory that has been delegated certain privileges. While members of the **Domain Admins** group have sufficient privileges to connect to the directory, as a best practice, you should use a service account that only has the minimum privileges necessary to connect to the directory. The following procedure demonstrates how to create a new group called `Connectors`, delegate the necessary privileges that are needed to connect AWS Directory Service to this group, and then add a new service account to this group. +To connect to your existing directory, you must have the credentials for your AD Connector service account in the existing directory that has been delegated certain privileges. While members of the **Domain Admins** group have sufficient privileges to connect to the directory, as a best practice, you should use a service account that only has the minimum privileges necessary to connect to the directory. The following procedure demonstrates how to create a new group called `Connectors`, delegate the necessary privileges that are needed to connect Directory Service to this group, and then add a new service account to this group. @@ -271 +271 @@ If you will be using Seamless Domain Join or WorkSpaces, you must also enable ** - 12. Create a user account with a strong password and add that user to the `Connectors` group. This user will be known as your AD Connector service account and since it is now a member of the `Connectors` group it now has sufficient privileges to connect AWS Directory Service to the directory. + 12. Create a user account with a strong password and add that user to the `Connectors` group. This user will be known as your AD Connector service account and since it is now a member of the `Connectors` group it now has sufficient privileges to connect Directory Service to the directory.