Commit cd996c5c authored by Drew Blessing's avatar Drew Blessing

Replace EFS section in AWS guide

parent acb72a8e
...@@ -7,11 +7,13 @@ supported natively in NFS version 4. NFSv3 also supports locking as long as ...@@ -7,11 +7,13 @@ supported natively in NFS version 4. NFSv3 also supports locking as long as
Linux Kernel 2.6.5+ is used. We recommend using version 4 and do not Linux Kernel 2.6.5+ is used. We recommend using version 4 and do not
specifically test NFSv3. specifically test NFSv3.
## AWS Elastic File System (EFS) not recommended ## AWS Elastic File System
GitLab does not recommend using AWS Elastic File System (EFS).
Customers and users have reported that AWS EFS does not perform well for GitLab's Customers and users have reported that AWS EFS does not perform well for GitLab's
use-case. There are several issues that can cause problems. For these reasons use-case. There are several issues that can cause problems. For these reasons
GitLab recommends against using EFS with GitLab. GitLab does not recommend using EFS with GitLab.
- EFS bases allowed IOPS on volume size. The larger the volume, the more IOPS - EFS bases allowed IOPS on volume size. The larger the volume, the more IOPS
are allocated. For smaller volumes, users may experience decent performance are allocated. For smaller volumes, users may experience decent performance
...@@ -22,7 +24,7 @@ GitLab recommends against using EFS with GitLab. ...@@ -22,7 +24,7 @@ GitLab recommends against using EFS with GitLab.
EBS with an NFS server on top will perform much better. EBS with an NFS server on top will perform much better.
For more details on another person's experience with EFS, see For more details on another person's experience with EFS, see
[Amazon's Elastic File System: Burst Credits]()https://www.rawkode.io/2017/04/amazons-elastic-file-system-burst-credits/ [Amazon's Elastic File System: Burst Credits](https://www.rawkode.io/2017/04/amazons-elastic-file-system-burst-credits/)
### Recommended options ### Recommended options
......
...@@ -159,19 +159,21 @@ subnet and security group and ...@@ -159,19 +159,21 @@ subnet and security group and
*** ***
## Elastic File System ## Network File System
This new AWS offering allows us to create a file system accessible by
 GitLab requires a shared filesystem such as NFS. The file share(s) will be
EC2 instances within a VPC. Choose our VPC and the subnets will be mounted on all application servers. There are a variety of ways to build an

automatically configured assuming we don't need to set explicit IPs. NFS server on AWS.
The
next section allows us to add tags and choose between General
Purpose or
Max I/O which is a good option when being accessed by a
large number of
EC2 instances.


![Elastic File System](img/elastic-file-system.png) One option is to use a third-party AMI that offers NFS as a service. A [search
for 'NFS' in the AWS Marketplace](https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=NFS&page=1&ref_=nav_search_box)
shows options such as NetApp, SoftNAS and others.
To actually mount and install the NFS client we'll use the User Data Another option is to build a simple NFS server using a vanilla Linux server backed
section when adding our Launch Configuration. by AWS Elastic Block Storage (EBS).
> **Note:** GitLab does not recommend using AWS Elastic File System (EFS). See
details in [High Availability NFS documentation](../../../administration/high_availability/nfs.md#aws-elastic-file-system)
*** ***
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment