AWS Security ChangesHomeSearch

AWS fsx medium security documentation change

Service: fsx · 2025-11-07 · Security-related medium

File: fsx/latest/WindowsGuide/unable-to-create-fs.md

Summary

Added troubleshooting guidance for Secrets Manager credential access issues and domain join errors

Security assessment

The changes add documentation about securing Active Directory credentials through AWS Secrets Manager, including required permissions and secret validation. This addresses potential security risks from misconfigured credentials by enforcing proper secret management practices. Specific security evidence includes requirements for resource-based policies granting FSx access to secrets and validation of credential fields.

Diff

diff --git a/fsx/latest/WindowsGuide/unable-to-create-fs.md b/fsx/latest/WindowsGuide/unable-to-create-fs.md
index 6c08b4ae7..51c3387a1 100644
--- a//fsx/latest/WindowsGuide/unable-to-create-fs.md
+++ b//fsx/latest/WindowsGuide/unable-to-create-fs.md
@@ -5 +5 @@
-Misconfigured VPC security groupDuplicate file system administrators group namesDNS servers or domain controllers unreachableInvalid service account credentialsInsufficient service account permissionsService account capacity exceededCan't access the OUBad file system admin groupAmazon FSx lost connectivity in domainService account does not have correct permissionsUnicode characters used in creation parametersSwitching storage type to HDD while restoring a backup fails
+Misconfigured VPC security groupDuplicate file system administrators group namesDNS servers or domain controllers unreachableInvalid service account credentialsAmazon FSx can't access your Active Directory service account credentials in AWS Secrets ManagerInsufficient service account permissionsService account capacity exceededCan't access the OUBad file system admin groupAmazon FSx lost connectivity in domainService account does not have correct permissionsUnicode characters used in creation parametersSwitching storage type to HDD while restoring a backup fails
@@ -20,0 +21,2 @@ There are a number of potential causes when a file system creation request fails
+  * Amazon FSx can't access your Active Directory service account credentials in AWS Secrets Manager
+
@@ -118,0 +121,19 @@ Use the following steps to troubleshoot and resolve the issue.
+**Case 1: If you are using an AWS Secrets Manager secret to store your Active Directory credentials**
+
+  1. Review [Storing Active Directory credentials using AWS Secrets Manager](./self-managed-AD.html#bp-store-ad-creds-using-secret-manager-windows).
+
+  2. at the secret ARN is correct and follows the proper format: `arn:aws:secretsmanager:region:account-id:secret:secret-name-6chars`.
+
+  3. Verify that the secret contains both required fields with non-empty values:
+
+     * `CUSTOMER_MANAGED_ACTIVE_DIRECTORY_USERNAME` – Your AD service account username.
+
+     * `CUSTOMER_MANAGED_ACTIVE_DIRECTORY_PASSWORD` – Your AD service account password.
+
+  4. Verify that the secret and key have a resource-based policy that grants the Amazon FSx service principal `fsx.amazonaws.com` permission to retrieve the secret value. 
+
+
+
+
+**Case 2: If you are using plaintext credentials to join your Active Directory**
+
@@ -143,0 +165,67 @@ For more information about creating a service account with correct permissions,
+## 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 a file system 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 a file system 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.html#bp-store-ad-creds-using-secret-manager-windows).
+
+  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 a file system 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.html#bp-store-ad-creds-using-secret-manager-windows).
+
+  2. Verify that the Secrets Manager secret you are providing has the correct policies that allow Amazon FSx to use the secret.
+
+
+
+
+**Joining a file system 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 a file system 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.html#bp-store-ad-creds-using-secret-manager-windows).
+
+  2. Verify that the Secrets Manager secret you are providing has both of the required fields.
+
+
+
+