I am thinking of using a self-managed Windows Server with FSx for WindowsServer.
It works fine from an EC2 inside the same VPC, checked with AmazonFSxADValidation.
However, when I try to create it, I get the following error
File system creation failed. Amazon FSx is unable to communicate with your Microsoft Active Directory domain controller(s).
This is because Amazon FSx can't reach the DNS servers provided or domain controllers for your domain.
To fix this problem, delete your file system and create a new one with valid DNS servers and networking configuration that allows traffic from the file system to the domain controller as recommended in the Amazon FSx user guide: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-manage-prereqs.html.
Do you know the cause?
Note that we are using Route53 for DNS, not Windows Server, and the necessary records in netlogon have already been created.
I really appreciate any help you can provide.
AWS OFFICIALAktualisiert vor einem Jahr
I thought I had succeeded because the check tool showed no errors. ....
I suggest you troubleshoot according to the troubleshooting instructions in the document I shared.
I followed the recommendations and wrote FireWall, etc., but it remained the same.