FSx for Windows File Server with self-managed AD

Question

A customer has deployed an Amazon FSx for Windows File Server joined to his self-managed Active Directory. He noticed that Amazon FSx is creating 4 different computer objects into its OU for 1 file system, 4 new computer objects for another file system, etc. which will result in a very difficult situation to manage those file systems at scale.

[Nothing in particular is mentioned within our documentation except to not move computer objects that Amazon FSx creates in the OU after your file system is created][1]

Is it the normal behavior of Amazon FSx for Windows File Server with self-managed AD? Do you have any clue which may help to better understand Amazon FSx behavior? Thank you very much in advance for your feedback

[1]: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD-best-practices.html

Accepted Answer

Amazon FSx (Multi-AZ or Single-AZ2) creates a cluster, so the objects in the OU represent cluster nodes as well as cluster itself - that's why you see multiple objects.
Instead of moving FSx objects to different OUs you may just create an OU in your AD dedicated to FSx and specify that OU when you create an FSx file system joined to a self-managed AD.

FSx for Windows File Server with self-managed AD

Relevant content