From 4e0f26712036e1ce320680c179cb01ec0eed762a Mon Sep 17 00:00:00 2001 From: Benjamin Wilson Date: Wed, 14 Dec 2016 20:41:35 -0500 Subject: [PATCH] Update wording, remove possibly incorrect Windows info --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3537d20..d69a388 100644 --- a/README.md +++ b/README.md @@ -944,7 +944,9 @@ EFS - πŸ”Έ As of 2016-11, EFS does not offer disk level encryption, though it is on the roadmap. - ❗ Some applications, like SQLite and IPython, [might not work properly](https://sqlite.org/faq.html#q5) on EFS when accessed from multiple clients. This is because lock upgrades and downgrades are [not supported](http://docs.aws.amazon.com/efs/latest/ug/nfs4-unsupported-features.html). There might be [workarounds](https://github.com/ipython/ipython/issues/882) for some issues. - πŸ”Έ Mounting EFS over a VPN connection or VPC peering is not supported. EFS [does support](https://aws.amazon.com/efs/faq/#on-premises) mounting over Direct Connect. -- πŸ”Έ Using an EFS volume on Windows is not supported because the Window NFS client does not support NFS v4 or v4.1. +- πŸ”Έ An EFS file system can be mounted on premises over Direct Connect. +- πŸ”Έ An EFS file system can NOT be mounted over VPC peering or VPN, even if the VPN is running on top of Direct Connect. +- πŸ”Έ Using an EFS volume on Windows is not supported. - ⏱ When a file is uploaded to EFS, it can take hours for EFS to update the details for billing and burst credit purposes. - πŸ”Έβ± Metadata operations can be costly in terms of burst credit consumption. Recursively traversing a tree containing thousands of files can easily ramp up to tens or even hundreds of megabytes of burst credits being consumed, even if no file is being touched. Commands like ```find``` or ```chown -R``` can have an adverse impact on performace if run periodically. - πŸ”Έ Mount points are AZ-based. In an Auto scaling group spread across zones, you can end up with instances in one zone mounting EFS from a different zone. That might decrease performance and would create an unintended single point of failure. One way to fix it would be [a shell script](https://gist.github.com/bgdnlp/9fd326dc4a23f46bab93a1eade023fe4) that runs before network drives are mounted and edits /etc/fstab with the proper AZ.