AWS fsx high security documentation change
Summary
Added new misconfiguration scenario for Secrets Manager/KMS key setup and resolution steps
Security assessment
Identifies security risks from improper Secrets Manager/KMS configurations that could lead to credential exposure or authentication failures. Provides mitigation steps for secure configuration.
Diff
diff --git a/fsx/latest/WindowsGuide/misconfigured-ad-config.md b/fsx/latest/WindowsGuide/misconfigured-ad-config.md index 0df7985c3..aa6434e63 100644 --- a//fsx/latest/WindowsGuide/misconfigured-ad-config.md +++ b//fsx/latest/WindowsGuide/misconfigured-ad-config.md @@ -5 +5 @@ -Misconfigured file system: Amazon FSx can't reach either the DNS servers or domain controllers for your domain.Misconfigured file system: The service account credentials are invalidMisconfigured file system: The service account provided doesn't have permission to join the file system to the domainMisconfigured file system: The service account can't join any more computers to domainMisconfigured file system: The service account doesn't have access to the OU +Misconfigured file system: Amazon FSx can't reach either the DNS servers or domain controllers for your domain.Misconfigured file system: The service account credentials are invalidMisconfigured file system: The AWS Secrets Manager secret or KMS key is not configured correctlyMisconfigured file system: The service account provided doesn't have permission to join the file system to the domainMisconfigured file system: The service account can't join any more computers to domainMisconfigured file system: The service account doesn't have access to the OU @@ -39,0 +40,2 @@ Other issues may not require changing any Active Directory configuration paramet + * Misconfigured file system: The AWS Secrets Manager secret or KMS key is not configured correctly + @@ -90,0 +93,19 @@ You can also use the Amazon FSx API operation `update-file-system`. To learn mor +## Misconfigured file system: The AWS Secrets Manager secret or KMS key is not configured correctly + +Amazon FSx can't establish a connection with your Microsoft Active Directory domain controller or controllers. This is because your AWS Secrets Manager secret or AWS KMS key is not configured correctly. For more information, see [Storing Active Directory credentials using AWS Secrets Manager](./self-managed-AD.html#bp-store-ad-creds-using-secret-manager-windows). + +To resolve the misconfiguration, do the following: + + 1. Verify that the secret ARN is correct and follows the proper format: `arn:aws:secretsmanager:region:account-id:secret:secret-name-6chars`. + + 2. 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. + + * 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. + + + +