AWS privateca: Add directory registration troubleshooting cross-reference
Summary
Extends the DIRECTORY_ACCESS_DENIED remediation with a link to the directory registration failure troubleshooting page and renames a heading from 'SPN creation failure' to 'Directory registration failure'.
Security assessment
The edit only appends a cross-reference link and renames a heading; the existing IAM/permission guidance is unchanged, so no new security content is added.
Evidence
+`DIRECTORY_ACCESS_DENIED` | Connector for AD unable to access your directory. | You must grant Connector for AD access to your directory. Review the [Step 4: Create IAM Policy](./connector-for-ad-getting-started-prerequisites.html#prereq-iam) section to make sure that you the IAM policy associated with your AWS account enables you to access and describe directories. After granting the correct permissions to your AWS role, delete the failed connector and create a new one. If using Connector for AD with an AWS Directory Service AD Connector, make sure that the AD Connector service account's password isn't expired and is valid. For information about AD Connector service accounts, see [Getting started with AD Connector](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ad_connector_getting_started.html) in the _AD Connector Administration Guide_. For information about troubleshooting `DIRECTORY_ACCESS_DENIED` and other failures on directory registrations, see [Troubleshoot Connector for AD directory registration failures](./c4adTroubleshootingDirectoryRegistrationFailure.html).
Diff
diff --git a/privateca/latest/userguide/c4adTroubleshootingConnectorCreationFailure.md b/privateca/latest/userguide/c4adTroubleshootingConnectorCreationFailure.md index e19f2a7f1..feff77722 100644 --- a//privateca/latest/userguide/c4adTroubleshootingConnectorCreationFailure.md +++ b//privateca/latest/userguide/c4adTroubleshootingConnectorCreationFailure.md @@ -14 +14 @@ Failure status | Description | Remediation -`DIRECTORY_ACCESS_DENIED` | Connector for AD unable to access your directory. | You must grant Connector for AD access to your directory. Review the [Step 4: Create IAM Policy](./connector-for-ad-getting-started-prerequisites.html#prereq-iam) section to make sure that you the IAM policy associated with your AWS account enables you to access and describe directories. After granting the correct permissions to your AWS role, delete the failed connector and create a new one. If using Connector for AD with an AWS Directory Service AD Connector, make sure that the AD Connector service account's password isn't expired and is valid. For information about AD Connector service accounts, see [Getting started with AD Connector](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ad_connector_getting_started.html) in the _AD Connector Administration Guide_. +`DIRECTORY_ACCESS_DENIED` | Connector for AD unable to access your directory. | You must grant Connector for AD access to your directory. Review the [Step 4: Create IAM Policy](./connector-for-ad-getting-started-prerequisites.html#prereq-iam) section to make sure that you the IAM policy associated with your AWS account enables you to access and describe directories. After granting the correct permissions to your AWS role, delete the failed connector and create a new one. If using Connector for AD with an AWS Directory Service AD Connector, make sure that the AD Connector service account's password isn't expired and is valid. For information about AD Connector service accounts, see [Getting started with AD Connector](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/ad_connector_getting_started.html) in the _AD Connector Administration Guide_. For information about troubleshooting `DIRECTORY_ACCESS_DENIED` and other failures on directory registrations, see [Troubleshoot Connector for AD directory registration failures](./c4adTroubleshootingDirectoryRegistrationFailure.html). @@ -33 +33 @@ Connector for AD error codes -SPN creation failure +Directory registration failure