AWS directoryservice documentation change
Summary
Fixed URL formatting (added double slashes), updated product name references to 'Directory Service', and corrected documentation links
Security assessment
Changes involve URL syntax corrections, branding updates, and link fixes. No security-related content was added or modified. Troubleshooting steps and guidance remain functionally unchanged.
Diff
diff --git a/directoryservice/latest/admin-guide/ad_connector_troubleshooting.md b/directoryservice/latest/admin-guide/ad_connector_troubleshooting.md index a073e3dcf..471f309ed 100644 --- a//directoryservice/latest/admin-guide/ad_connector_troubleshooting.md +++ b//directoryservice/latest/admin-guide/ad_connector_troubleshooting.md @@ -41 +41 @@ The following can help you troubleshoot some common issues you might encounter w -Some AWS accounts created before 2012 might have access to Availability Zones in the US East (N. Virginia), US West (N. California), or Asia Pacific (Tokyo) Regions that do not support AWS Directory Service directories. If you receive an error such as this when creating a Active Directory, choose a subnet in a different Availability Zone and try to create the directory again. +Some AWS accounts created before 2012 might have access to Availability Zones in the US East (N. Virginia), US West (N. California), or Asia Pacific (Tokyo) Regions that do not support Directory Service directories. If you receive an error such as this when creating a Active Directory, choose a subnet in a different Availability Zone and try to create the directory again. @@ -86 +86 @@ AD Connector uses the Active Directory Site whose subnet IP address ranges are c -You can use [network packet capture](https://techcommunity.microsoft.com/blog/iis-support-blog/capture-a-network-trace-without-installing-anything--capture-a-network-trace-of-/376503) on your domain controllers, DNS servers, and VPC flow logs of directory network interfaces to investigate this issue. Contact [AWS Support](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html) for further assistance. +You can use [network packet capture](https://techcommunity.microsoft.com/blog/iis-support-blog/capture-a-network-trace-without-installing-anything--capture-a-network-trace-of-/376503) on your domain controllers, DNS servers, and VPC flow logs of directory network interfaces to investigate this issue. Contact [AWS Support](https://docs.aws.amazon.com//awssupport/latest/user/case-management.html) for further assistance. @@ -238 +238 @@ The Certificate Authority (CA) certificates should be uploaded to the AD Connect -For more information about publishing certificates to the NTAuth store, see [Import the issuing CA certificate into the Enterprise NTAuth store](https://docs.aws.amazon.com/whitepapers/latest/access-workspaces-with-access-cards/import-the-issuing-ca-certificate-into-the-enterprise-ntauth-store.html) in _Access Amazon WorkSpaces with Common Access Cards Installation Guide_. +For more information about publishing certificates to the NTAuth store, see [Import the issuing CA certificate into the Enterprise NTAuth store](https://docs.aws.amazon.com//whitepapers/latest/access-workspaces-with-access-cards/import-the-issuing-ca-certificate-into-the-enterprise-ntauth-store.html) in _Access Amazon WorkSpaces with Common Access Cards Installation Guide_. @@ -265 +265 @@ This can occur if the hard drive on your domain controller runs out of space. En -The following errors or symptoms occur while searching users in AWS Enterprise Applications such as [Amazon WorkSpaces Console Launch Wizard](https://docs.aws.amazon.com/workspaces/latest/adminguide/launch-workspace-ad-connector.html#create-workspace-ad-connector): +The following errors or symptoms occur while searching users in AWS Enterprise Applications such as [Amazon WorkSpaces Console Launch Wizard](https://docs.aws.amazon.com//workspaces/latest/adminguide/launch-workspace-ad-connector.html#create-workspace-ad-connector): @@ -426 +426 @@ If seamless domain join for EC2 instances was working and then stopped while the - 2. Update the password for the service account in your AD Connector in AWS Directory Service. For more information, see [Updating your AD Connector service account credentials in AWS Management Console](./ad_connector_update_creds.html). + 2. Update the password for the service account in your AD Connector in Directory Service. For more information, see [Updating your AD Connector service account credentials in AWS Management Console](./ad_connector_update_creds.html). @@ -433 +433 @@ If seamless domain join for EC2 instances was working and then stopped while the -Updating the password only in AWS Directory Service does not push the password change to your existing on-premises Active Directory so it is important to do it in the order shown in the previous procedure. +Updating the password only in Directory Service does not push the password change to your existing on-premises Active Directory so it is important to do it in the order shown in the previous procedure. @@ -456 +456 @@ You can use the built-in Windows package capture utility ([netsh](https://learn. -To better understand what requests are being received and sent from AD Connector, you can configure [VPC flow logs](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-flow-logs.html) for the directory network interfaces. You can identify all network interfaces reserved for use with AWS Directory Service by the description: `AWS created network interface for directory `your-directory-id``. +To better understand what requests are being received and sent from AD Connector, you can configure [VPC flow logs](https://docs.aws.amazon.com//vpc/latest/userguide/working-with-flow-logs.html) for the directory network interfaces. You can identify all network interfaces reserved for use with Directory Service by the description: `AWS created network interface for directory `your-directory-id``.