Docs feedback: Suggestion for adding notes on additional scenarios

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Label this issue
  • Close this issue

It would be helpful to add additional tips, cautions or notes in this instruction set on best practices for setting up Gitlab HA on AWS.

  • In the storage section for deploying gitlab in an autoscale group, a tip or note on using gitaly as the backend store instead of NFS could point to the following link: https://about.gitlab.com/2018/09/12/the-road-to-gitaly-1-0/

  • I noticed that a NAT Gateway isn't included in the VPC setup. If this would be helpful with security, perhaps a tip could be added.

I'm making these suggestions because there are alternative external guides on the setup of gitlab with AWS that have different (and apparently deprecated) approaches. For example, the following guide explains how to do this with terraform:

https://medium.com/@aloisbarreras_18569/automating-running-gitlab-on-aws-with-terraform-packer-and-ansible-bf1c8724ebea

It would be helpful to outline the best approach and the rationale for these approaches.

Thanks!

J

Edited Jun 30, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading