"Amazon FSx is unable to communicate with your Microsoft Active Directory domain controller"

0

Hello! I am trying to set up FSx for use with my AWS-managed Active Directory, but I receive the following error:

File system creation failed. Amazon FSx is unable to communicate with your Microsoft Active Directory domain controller(s).

I am struggling to figure out why this is happening. The ACLs allow for all inbound and outbound traffic (I have also tried restricting them to just the ports mentioned in the documentation, but had no luck) and Amazon's AD validation tool doesn't report any issues.

I am not sure how relevant the following is, but oddly enough when I attempt to create an FSx drive in its own security group and different subnets, the FSx creation takes 20 minutes before it fails. If I use our AD's details, it takes about 6 hours before failing (and this time has been persisting through multiple attempts for a week now).

Is there anything else I could try or check?

1 個回答
3

Hi,

In order to successfully create Amazon FSx for Windows File Server, Amazon FSx requires that every single domain controller in the Active Directory domain is reachable. This is because during validation, Amazon FSx uses a DC locator algorithm that can select any of the domain controllers. If you have multiple domain controllers, ensure that all of them meet the requirements listed in the below link, and ensure that any changes to your service account are propagated to all domain controllers. https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-manage-prereqs.html

As a best practice, we recommend that customer uses Active Directory Sites & Services to ensure that FSx connects to a single domain controller site. This is important so as to avoid AD object replication delays as well as network connectivity issues across AD sites.

AWS
bodep
已回答 1 年前
profile pictureAWS
專家
Rob_H
已審閱 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南