Data residency and high availability
- Tier: Ultimate
- Offering: GitLab Dedicated
GitLab Dedicated provides data residency control, infrastructure isolation, and high availability through single-tenant AWS deployments.
Data isolation
GitLab Dedicated isolates your data and infrastructure from other tenants through single-tenant architecture:
- Your environment runs in an AWS account separate from other tenants.
- All infrastructure required to host GitLab is contained within your account boundary.
- Your data remains within your account and is isolated from GitLab.com.
- You administer the application while GitLab manages the underlying infrastructure.
Data residency
During onboarding, you select AWS regions for your instance deployment, data storage, and disaster recovery to meet compliance, performance, and availability requirements.
Primary regions
You can deploy your instance in the following AWS regions:
| Region | Code |
|---|---|
| Africa (Cape Town) | af-south-1 |
| Asia Pacific (Hyderabad) | ap-south-2 |
| Asia Pacific (Jakarta) | ap-southeast-3 |
| Asia Pacific (Mumbai) | ap-south-1 |
| Asia Pacific (Osaka) | ap-northeast-3 |
| Asia Pacific (Seoul) | ap-northeast-2 |
| Asia Pacific (Singapore) | ap-southeast-1 |
| Asia Pacific (Sydney) | ap-southeast-2 |
| Asia Pacific (Tokyo) | ap-northeast-1 |
| Canada (Central) | ca-central-1 |
| Europe (Frankfurt) | eu-central-1 |
| Europe (Ireland) | eu-west-1 |
| Europe (London) | eu-west-2 |
| Europe (Milan) | eu-south-1 |
| Europe (Paris) | eu-west-3 |
| Europe (Stockholm) | eu-north-1 |
| Europe (Zurich) | eu-central-2 |
| Israel (Tel Aviv) | il-central-1 |
| Middle East (Bahrain) | me-south-1 |
| South America (São Paulo) | sa-east-1 |
| US East (Ohio) | us-east-2 |
| US East (N. Virginia) | us-east-1 |
| US West (N. California) | us-west-1 |
| US West (Oregon) | us-west-2 |
For low emission region guidance, see choose a region based on both business requirements and sustainability goals.
If you need a region that isn’t listed, contact your account representative or GitLab Support.
Secondary regions with limited support
You can select AWS regions as secondary regions for disaster recovery, but they don’t support all AWS features that GitLab Dedicated uses. Some features are unavailable if failover occurs to your secondary region.
The following regions are available only as secondary regions and don’t support AWS Simple Email Service (SES):
| Region | Code |
|---|---|
| Asia Pacific (Hong Kong) | ap-east-1 |
| Asia Pacific (Melbourne) | ap-southeast-4 |
| Asia Pacific (Malaysia) | ap-southeast-5 |
| Asia Pacific (Thailand) | ap-southeast-7 |
| Canada West (Calgary) | ca-west-1 |
| Europe (Spain) | eu-south-2 |
| Mexico (Central) | mx-central-1 |
Without SES support, you cannot send email notifications using the default configuration. To maintain email functionality in these regions, set up an external SMTP mail service.
During onboarding, regions with limitations are clearly marked. You must acknowledge the associated risks before selecting one as your secondary region.
Availability and scalability
GitLab Dedicated uses modified versions of the Cloud Native Hybrid reference architectures with high availability configurations.
GitLab matches your instance to the closest reference architecture size based on your number of users.
GitLab Dedicated environments use additional cloud provider services beyond the standard reference architectures to enhance security and stability. As a result, GitLab Dedicated costs differ from standard reference architecture costs.