Just incase anyone runs into this again. Our primary problem was implementation of our aws/dns. We were able to go into the infrastructure container for efs and look about how it couldn’t connect. Otherwise almost no configuration was needed.
Rancher assumes its going to be able to mount efs based on the dns cname. So depending on how you have your dns resolution in place this can potentially kill it. For example if you are using 188.8.131.52, 184.108.40.206 as your dns servers they won’t be able to resolve the efs cname.
You will need to be using amazon’s internal dns (10.0.0.0/8 ==> 10.0.0.2) so you can resolve correctly.