{::options parse_block_html="true" /}
Provision GitLab Instances on AWS EKS (FREE SELF)
Available Infrastructure as Code for GitLab Instance Installation on AWS
The GitLab Environment Toolkit (GET) is a set of opinionated Terraform and Ansible scripts. These scripts help with the deployment of Linux package or Cloud Native Hybrid environments on selected cloud providers and are used by GitLab developers for GitLab Dedicated (for example).
You can use the GitLab Environment Toolkit to deploy a Cloud Native Hybrid environment on AWS. However, it's not required and may not support every valid permutation. That said, the scripts are presented as-is and you can adapt them accordingly.
Two and Three Zone High Availability
While GitLab Reference Architectures generally encourage three zone redundancy, AWS Quick Starts and AWS Well Architected consider two zone redundancy as AWS Well Architected. Individual implementations should weigh the costs of two and three zone configurations against their own high availability requirements for a final configuration.
Gitaly Cluster uses a consistency voting system to implement strong consistency between synchronized nodes. Regardless of the number of availability zones implemented, there will always need to be a minimum of three Gitaly and three Praefect nodes in the cluster to avoid voting stalemates cause by an even number of nodes.
AWS PaaS qualified for all GitLab implementations
For both implementations that used the Linux package or Cloud Native Hybrid implementations, the following GitLab Service roles can be performed by AWS Services (PaaS). Any PaaS solutions that require preconfigured sizing based on the scale of your instance will also be listed in the per-instance size Bill of Materials lists. Those PaaS that do not require specific sizing, are not repeated in the BOM lists (for example, AWS Certification Manager).
These services have been tested with GitLab.
Some services, such as log aggregation, outbound email are not specified by GitLab, but where provided are noted.
| GitLab Services | AWS PaaS (Tested) | Provided by AWS Cloud Native Hybrid Quick Start |
|---|---|---|
| Tested PaaS Mentioned in Reference Architectures | ||
| PostgreSQL Database | Amazon RDS PostgreSQL | Yes. |
| Redis Caching | Redis ElastiCache | Yes. |
|
Gitaly Cluster (Git Repository Storage) (Including Praefect and PostgreSQL) |
ASG and Instances | Yes - ASG and Instances Note: Gitaly cannot be put into a Kubernetes Cluster. |
|
All GitLab storages besides Git Repository Storage (Includes Git-LFS which is S3 Compatible) |
AWS S3 | Yes |
| Tested PaaS for Supplemental Services | ||
| Front End Load Balancing | AWS ELB | Yes |
| Internal Load Balancing | AWS ELB | Yes |
| Outbound Email Services | AWS Simple Email Service (SES) | Yes |
| Certificate Authority and Management | AWS Certificate Manager (ACM) | Yes |
| DNS | AWS Route53 (tested) | Yes |
| GitLab and Infrastructure Log Aggregation | AWS CloudWatch Logs | Yes (ContainerInsights Agent for EKS) |
| Infrastructure Performance Metrics | AWS CloudWatch Metrics | Yes |
| Supplemental Services and Configurations (Tested) | ||
| Prometheus for GitLab | AWS EKS (Cloud Native Only) | Yes |
| Grafana for GitLab | AWS EKS (Cloud Native Only) | Yes |
| Administrative Access to GitLab Backend | Bastion Host in VPC | Yes - HA - Preconfigured for Cluster Management. |
| Encryption (In Transit / At Rest) | AWS KMS | Yes |
| Secrets Storage for Provisioning | AWS Secrets Manager | Yes |
| Configuration Data for Provisioning | AWS Parameter Store | Yes |
| AutoScaling Kubernetes | EKS AutoScaling Agent | Yes |