AWS fsx medium security documentation change
Summary
Added documentation about Secrets Manager credential access issues and expanded Active Directory terminology
Security assessment
The changes add multiple error scenarios related to AWS Secrets Manager credential management, including permission issues (FSx service principal access), secret format validation, and credential exposure prevention. These changes address security-related misconfigurations that could lead to authentication failures or credential exposure.
Diff
diff --git a/fsx/latest/ONTAPGuide/cannot-join-svm-to-ad.md b/fsx/latest/ONTAPGuide/cannot-join-svm-to-ad.md index 918e2532b..c5f26e049 100644 --- a//fsx/latest/ONTAPGuide/cannot-join-svm-to-ad.md +++ b//fsx/latest/ONTAPGuide/cannot-join-svm-to-ad.md @@ -5 +5 @@ -SVM NetBIOS name same as home domainSVM is joined to another ADSVM NetBIOS name already usedFSx can't reach AD domain controllersInsufficient port configuration or service account permissionsInvalid service account credentialsAmazon FSx can't connect to your Active Directory domain controllers because of insufficient service account credentialsCan't reach AD DNS servers or domain controllersInvalid AD domain nameService account can't access AD administrators groupSpecified OU is invalid +SVM NetBIOS name same as home domainSVM is joined to another Active DirectorySVM NetBIOS name already usedAmazon FSx can't access your Active Directory service account credentials in AWS Secrets ManagerFSx can't reach Active Directory domain controllersInsufficient port configuration or service account permissionsInvalid service account credentialsAmazon FSx can't connect to your Active Directory domain controllers because of insufficient service account credentialsCan't reach Active Directory DNS servers or domain controllersInvalid Active Directory domain nameService account can't access Active Directory administrators groupSpecified OU is invalid @@ -18,0 +19,2 @@ If you're unable to join an SVM to an Active Directory (AD), first review [How j + * Amazon FSx can't access your Active Directory service account credentials in AWS Secrets Manager + @@ -44 +46 @@ Joining an SVM to your self-managed Active Directory fails with the following er -To resolve this issue, follow the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) to reattempt joining your SVM to your AD. Ensure that you use a NetBIOS name for your SVM that's different than the NetBIOS name of the Active Directory's home domain. +To resolve this issue, follow the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) to reattempt joining your SVM to your Active Directory. Ensure that you use a NetBIOS name for your SVM that's different than the NetBIOS name of the Active Directory's home domain. @@ -56 +58 @@ To resolve the issue, do the following: - 2. Follow the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) to reattempt joining your SVM to the new AD. + 2. Follow the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) to reattempt joining your SVM to the new Active Directory. @@ -63 +65 @@ To resolve the issue, do the following: -Creating an SVM joined to your self-managed AD fails with the following error message: +Creating an SVM joined to your self-managed Active Directory fails with the following error message: @@ -68,0 +71,67 @@ To resolve this issue, follow the procedure described in [Joining SVMs to Active +## Amazon FSx can't access your Active Directory service account credentials in AWS Secrets Manager + +The following sections describe common issues and how to resolve them. + +**Joining an SVM to your self-managed Active Directory fails with the following error message:** + +`You can't provide both username/password and a domain join service account secret to connect to your Active Directory. Provide only one set of credentials.` + +###### To resolve this issue + + 1. Choose whether you want to provide credentials stored in a Secrets Manager secret, or in plaintext. + + 2. When joining an Active Directory, only provide one of those parameters and not both. + + + + +**Joining an SVM to your self-managed Active Directory fails with the following error message:** + +`The domain join service account secret ARN format you entered isn't valid. Use the format: arn:partition:secretsmanager:region:account-id:secret:secret-name-6chars` + +###### To resolve this issue + + 1. Review [Storing Active Directory credentials using AWS Secrets Manager](./self-managed-AD-best-practices.html#bp-store-ad-creds-using-secret-manager). + + 2. Verify that the ARN format you are entering is correct. A correct format example is `arn:aws:secretsmanager:us-east-1:123456789012:secret:MyDatabaseSecret-Ab3d5f`. + + + + +**Joining an SVM to your self-managed Active Directory fails with the following error message:** + +`Amazon FSx can't access the domain join service account secret [ARN]. Add a resource permission to the secret that grants the FSx service principal (fsx.amazonaws.com) permission to access it.` + +###### To resolve this issue + + 1. Review [Storing Active Directory credentials using AWS Secrets Manager](./self-managed-AD-best-practices.html#bp-store-ad-creds-using-secret-manager). + + 2. Verify that the Secrets Manager secret you are providing has the correct policies that allow Amazon FSx to use the secret. + + + + +**Joining an SVM to your self-managed Active Directory fails with the following error message:** + +`You don't have permission to access the domain join service account secret [ARN]. A resource permission needs to be added to the secret to grant you access.` + +###### To resolve this issue + + * The Secrets Manager secret owner or administrator needs to give your account access to use this secret. For more information, see [Identity-based policies](https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_iam-policies.html). + + + + +**Joining an SVM to your self-managed Active Directory fails with the following error message:** + +`The domain join service account secret format or content isn't valid. Make sure the secret includes both CUSTOMER_MANAGED_ACTIVE_DIRECTORY_USERNAME and CUSTOMER_MANAGED_ACTIVE_DIRECTORY_PASSWORD fields with non-empty values.` + +###### To resolve this issue + + 1. Review [Storing Active Directory credentials using AWS Secrets Manager](./self-managed-AD-best-practices.html#bp-store-ad-creds-using-secret-manager). + + 2. Verify that the Secrets Manager secret you are providing has both of the required fields. + + + + @@ -71 +140 @@ To resolve this issue, follow the procedure described in [Joining SVMs to Active -Joining an SVM to your self-managed AD fails with the following error message: +Joining an SVM to your self-managed Active Directory fails with the following error message: @@ -86 +155 @@ To resolve this issue, do the following: -Joining an SVM to your self-managed AD fails with the following error message: +Joining an SVM to your self-managed Active Directory fails with the following error message: @@ -94 +163 @@ To resolve this issue, do the following: - 2. Review the service account requirements described in [Active Directory service account requirements](./self-manage-prereqs.html#ontap-ad-service-account-prereqs). Ensure that service account has the delegated permissions necessary to join your SVM to the AD domain using the specified organizational unit. + 2. Review the service account requirements described in [Active Directory service account requirements](./self-manage-prereqs.html#ontap-ad-service-account-prereqs). Ensure that service account has the delegated permissions necessary to join your SVM to the Active Directory domain using the specified organizational unit. @@ -195 +264 @@ For more information, see [Managing file systems with the ONTAP CLI](./managing- - 5. Use the procedure described in [Network configuration requirements](./self-manage-prereqs.html#ontap-ad-network-configs) to update your SVM's AD configuration using the correct IP addresses for your AD DNS servers. + 5. Use the procedure described in [Network configuration requirements](./self-manage-prereqs.html#ontap-ad-network-configs) to update your SVM's Active Directory configuration using the correct IP addresses for your Active Directory DNS servers. @@ -208 +277 @@ To resolve this issue, use the following procedure: - 1. Review the on-premises Active Directory domain name requirements described in [Information needed when joining an SVM to an Active Directory](./self-managed-AD-join.html#ad-info-for-svm-join) Make sure that the AD you are attempting to join meets that requirement. + 1. Review the on-premises Active Directory domain name requirements described in [Information needed when joining an SVM to an Active Directory](./self-managed-AD-join.html#ad-info-for-svm-join) Make sure that the Active Directory you are attempting to join meets that requirement. @@ -210 +279 @@ To resolve this issue, use the following procedure: - 2. Use the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) and reattempt joining your SVM to an AD. Be sure to use the correct format for the AD domain's FQDN. + 2. Use the procedure described in [Joining SVMs to Active Directory using the AWS Management Console, AWS CLI and API](./join-svm-to-ad.html) and reattempt joining your SVM to an Active Directory. Be sure to use the correct format for the Active Directory domain's FQDN. @@ -223 +292 @@ To resolve this issue, do the following: - 1. Review the information about [providing a domain group](./self-managed-AD-join.html#ad-info-for-svm-join) to perform administrative actions on your SVM. Make sure that you are using the correct name of the AD domain administrators group. + 1. Review the information about [providing a domain group](./self-managed-AD-join.html#ad-info-for-svm-join) to perform administrative actions on your SVM. Make sure that you are using the correct name of the Active Directory domain administrators group. @@ -242 +311 @@ To resolve this issue, do the following: - 3. Reattempt joining the SVM to the AD using [this procedure](./join-svm-to-ad.html) with the correct organization unit. + 3. Reattempt joining the SVM to the Active Directory using [this procedure](./join-svm-to-ad.html) with the correct organization unit.