Support custom DNS names and mount target IP address in the mount option

[krrenjith]

Currently mount only supports the target formats "fs_id:/" or "efs_fqdn:/". This is restricting the use of custom DNS servers. If the mount helper support custom DNS names or mount target IP addresses, customers can either setup a A record in their DNS server to resolve the mount target IP addresses or specify the IP address directly in the mount command.

Expected options:

mount -t efs myefs.mydomain.com:/ /mnt
mount -t efs 172.31.40.212:/ /mnt

[Cappuccinuo]

Thanks for the feature request. We will have someone take a look.

[colliwhopper]

same issue

[briantist]

Any news on this? I set up my own DNS records for my EFS mount points due to the inflexibility of the Amazon ones, and to support latency-based routing records for two EFS filesystems that are in different regions. So for example I had:

• us-east-1.efs.example.com (round-robin to all us-east-1 mount points)
• us-west-1.efs.example.com (round-robin to all us-west-1 mount points)
• efs.example.com (latency-based routing, returns either of the above depending on latency)

Anyway, it worked flawlessly with straight NFS mounting, but then I wanted to enforce encryption in transit and use an access points so I had to use efs-utils, and the experience has not been great.

Not only can I not use any of these records, if I'm mounting cross-region, I need to embed a single IP and manipulate the text in the single config file to change the region (see #101).

---

Since this will probably come up, I want to address the issue of hitting a mount in a different region/VPC/AZ.

The choices made in the efs-utils currently seem to be based on trying to connect to a mount in the same AZ (necessarily: the same region) that you are connecting from.

This makes a lot of sense for many use cases like long-running clients, and I/O intensive workloads, as it will give the best performance & reliability, and help avoid extra cost.

But I think it's unnecessarily restrictive in the UX, especially for use cases that would benefit from easy connectivity that doesn't need to be long-lived and isn't really I/O intensive (example #140 (comment)).

So by all means keep the original idea as the default, even go ahead make us add extra options to override when we would be mounting over an unideal path, but please provide some way for us to use custom DNS records to make this process easier.

[plaformsre]

Any update from AWS side to enable custom DNS for EFS file system?