Has anyone ever got Windows Server to connect to an AWS EFS volume using the Windows NFS 4.1 client? I am aware it is unsupported but wondering if anyone had done it (or via another client or utility?)
We have a requirement for a Windows Server to drop files onto an NFS volume (ideally EFS) where a folder on that volume can be polled from a RHEL based application. That app doesnt support S3 else we'd use that
Tks
Starting from the NFSv4.1 client made by folks at CITI @ University of Michigan, with a few relatively minor changes, you can get a working connection to an AWS EFS filesystem.
As @kafka points out: AWS EFS disallows / fails when any client specifies a share deny value other than OPEN4_SHARE_DENY_NONE
. Luckily the CITI folks discovered this as a possible problem and added a definition that, when commented out, will only ever use OPEN4_SHARE_DENY_NONE
for the share deny value.
Once this definition is commented out, then you need to recompile it for your system – relatively trivial if you use the versions of Visual Studio and WDK that the readme specifies. One gotcha was that the self-signed certificate process needs to not use the outdated Root Agency certificate (since it's only 512-bit). Use certreq
instead.
I'm working on collecting this knowledge into a fork of the CITI code at Github. (I'm sure you either solved your problem or moved on, but good luck to those folks who landed here from Google!)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With