The last configuration step is to [change the default file locations ](http://docs.gitlab.com/ee/administration/high_availability/nfs.html)
Finally, reconfigure GitLab for the change to take effect:
to make the EFS integration easier to manage.
Finally run reconfigure, you might find it useful to run a check and
a service status to make sure everything has been setup correctly.
```sh
```sh
sudo gitlab-ctl reconfigure
sudo gitlab-ctl reconfigure
```
You might also find it useful to run a check and a service status to make sure
everything has been setup correctly:
```sh
sudo gitlab-rake gitlab:check
sudo gitlab-rake gitlab:check
sudo gitlab-ctl status
sudo gitlab-ctl status
```
```
If everything looks good, copy the Elastic IP over to your browser and
If everything looks good, you should be able to reach GitLab in your browser.
test the instance manually.
### Setting up the EBS volume
### Setting up the EBS volume
...
@@ -498,15 +501,17 @@ The EBS volume will host the Git repositories data:
...
@@ -498,15 +501,17 @@ The EBS volume will host the Git repositories data:
})
})
```
```
where `/mnt/gitlab-data` the location where you will store the Git data.
1. Save the file and reconfigure GitLab:
1. Save the file and reconfigure GitLab:
```sh
```sh
sudo gitlab-ctl reconfigure
sudo gitlab-ctl reconfigure
```
```
To add more than one data volume, follow the same steps.
TIP: **Tip:**
If you wish to add more than one data volumes to store the Git repositories,
You can read more about [storing Git data in an alternative directory](../../administration/repository_storage_paths.md).
read the [repository storage paths docs](../../administration/repository_storage_paths.md).
### Setting up Gitaly
### Setting up Gitaly
...
@@ -514,15 +519,19 @@ Gitaly is a service that provides high-level RPC access to Git repositories.
...
@@ -514,15 +519,19 @@ Gitaly is a service that provides high-level RPC access to Git repositories.
It should be enabled and configured in a separate EC2 instance on the
It should be enabled and configured in a separate EC2 instance on the
[private VPC](#subnets) we configured previously.
[private VPC](#subnets) we configured previously.
Follow the [documentation to set it up](../../administration/gitaly/index.md).
Follow the [documentation to set up Gitaly](../../administration/gitaly/index.md).
### Using Amazon S3 object storage
### Using Amazon S3 object storage
The S3 object storage can be used for various GitLab objects:
GitLab stores many objects outside the Git repository, many of which can be
uploaded to S3. That way, you can offload the root disk volume of these objects
which would otherwise take much space.
-[How to store the LFS objects in S3](../../workflow/lfs/lfs_administration.md#s3-for-omnibus-installations)((Omnibus GitLab installations))
In particular, you can store in S3:
-[How to store Container Registry images to S3](../../administration/container_registry.md#container-registry-storage-driver)(Omnibus GitLab installations)
-[How to store GitLab CI job artifacts to S3](../../administration/job_artifacts.md#using-object-storage)(Omnibus GitLab installations)
