AWS directoryservice documentation change
Summary
Multiple typographical fixes (apostrophe normalization: 'can’t' → 'can't', 'couldn’t' → 'couldn't', 'haven’t' → 'haven't'). No technical content changes.
Security assessment
Changes are limited to punctuation formatting. The existing security guidance about certificate expiration checks and LDAPS configuration remains unmodified.
Diff
diff --git a/directoryservice/latest/admin-guide/ad_connector_troubleshooting.md b/directoryservice/latest/admin-guide/ad_connector_troubleshooting.md index c25925fc0..4e084320b 100644 --- a//directoryservice/latest/admin-guide/ad_connector_troubleshooting.md +++ b//directoryservice/latest/admin-guide/ad_connector_troubleshooting.md @@ -64 +64 @@ If your AD Connector does not meet these requirements, recreate your AD Connecto -This error usually occurs when the AD Connector fails to create and can’t connect to a valid domain controller for your self-managed Active Directory domain. +This error usually occurs when the AD Connector fails to create and can't connect to a valid domain controller for your self-managed Active Directory domain. @@ -79 +79 @@ AD Connector uses the Active Directory Site whose subnet IP address ranges are c - * Inconsistencies in DNS SRV records (These records use the following syntax: `_ldap._tcp._< DnsDomainName>_` and `_kerberos._tcp.<DnsDomainName>`) created in customer managed Active Directory domain. This can occur when AD Connector couldn’t find and connect to a valid domain controller based on these SRV records. + * Inconsistencies in DNS SRV records (These records use the following syntax: `_ldap._tcp._< DnsDomainName>_` and `_kerberos._tcp.<DnsDomainName>`) created in customer managed Active Directory domain. This can occur when AD Connector couldn't find and connect to a valid domain controller based on these SRV records. @@ -301 +301 @@ The AD Connector directory's service account resides in the customer managed Act - * You may face this issue, if [client-side LDAPS](./ad_connector_ldap_client_side.html) is enabled on AD Connector, and the certificates are expired. Ensure both server side certificate and CA certificate are valid, haven’t expired, and meets the requirements as per the [LDAPs documentation](./ad_connector_ldap_client_side.html#prereqs-ldap-client-side). + * You may face this issue, if [client-side LDAPS](./ad_connector_ldap_client_side.html) is enabled on AD Connector, and the certificates are expired. Ensure both server side certificate and CA certificate are valid, haven't expired, and meets the requirements as per the [LDAPs documentation](./ad_connector_ldap_client_side.html#prereqs-ldap-client-side). @@ -375 +375 @@ You may experience errors when searching for users or logging into AWS applicati - * If you’re not sure whether the password is expired or changed, you can reset the service account password and also [update](./ad_connector_update_creds.html) the same password in AD Connector. + * If you're not sure whether the password is expired or changed, you can reset the service account password and also [update](./ad_connector_update_creds.html) the same password in AD Connector. @@ -437 +437 @@ Updating the password only in AWS Directory Service does not push the password c -If your AD Connector switches to an inoperable state, you no longer have access to your domain controllers. We block the deletion of an AD Connector when there are still applications linked to it because one of those applications may still be using the directory. For a list of applications you need to disable in order to delete your AD Connector, see [Deleting your AD Connector](./ad_connector_delete.html). If you still can’t delete your AD Connector, you can request help through [AWS Support](https://aws.amazon.com/contact-us/). +If your AD Connector switches to an inoperable state, you no longer have access to your domain controllers. We block the deletion of an AD Connector when there are still applications linked to it because one of those applications may still be using the directory. For a list of applications you need to disable in order to delete your AD Connector, see [Deleting your AD Connector](./ad_connector_delete.html). If you still can't delete your AD Connector, you can request help through [AWS Support](https://aws.amazon.com/contact-us/).