doc/administration/dedicated/create_instance/data_residency_high_availability.md
{{< details >}}
{{< /details >}}
GitLab Dedicated provides data residency control and high availability capabilities through your choice of AWS regions. You control where your data is stored and processed, enabling you to meet regulatory requirements while maintaining enterprise-grade uptime.
Your GitLab Dedicated environment runs in a dedicated AWS account, completely isolated from other tenants and GitLab.com. This single-tenant architecture gives you full control over data location while GitLab manages the underlying infrastructure and ensures high availability through proven reference architectures.
GitLab Dedicated uses a modified version of the Cloud Native Hybrid reference architecture with high availability. Within your selected region, GitLab distributes your infrastructure across multiple availability zones for redundancy. During onboarding, you can let GitLab automatically select availability zones (recommended), or specify custom availability zone IDs to align with your existing AWS infrastructure.
[!note] GitLab Dedicated uses additional cloud provider services beyond the standard reference architectures to enhance security and stability. As a result, costs for GitLab Dedicated differ from standard reference architecture costs.
When you create your GitLab Dedicated instance, you select AWS regions for your primary deployment, disaster recovery, and backups. Your region choices are permanent and cannot be changed after provisioning. Choose regions based on data residency requirements, latency, and disaster recovery strategy to ensure your instance meets compliance needs and protects against regional outages.
Primary region : Your main deployment where your instance runs and users access GitLab. This is where your data is stored and must meet your data residency requirements.
Secondary region : An optional AWS region for Geo-based disaster recovery. If your primary region becomes unavailable, you can fail over to your secondary region.
Backup region : An optional AWS region where backups are replicated for additional redundancy. This can be the same as your primary or secondary region, or a different region for increased redundancy.
Consider these factors when selecting regions:
[!note] Regions with limitations are clearly marked, and you must acknowledge the associated risks before selecting them.
The following table shows all AWS regions supported by GitLab Dedicated. Any region in this table can be used as your primary, secondary, or backup region.
<!-- separator -->[!warning] US East (N. Virginia) dependency risk AWS hosts global identity and access management (IAM) services in the
us-east-1region. An outage inus-east-1prevents GitLab from performing operations on tenants, including failover to secondary regions. Tenants withus-east-1as their primary region experience downtime that GitLab cannot mitigate during an outage. Consider selecting a different primary region to reduce this risk.
[!warning] Middle East regions temporarily unavailable Both
me-central-1(UAE) andme-south-1(Bahrain) are currently unavailable due to significant infrastructure disruptions. Instances in these regions might experience prolonged downtime, service degradation, scaling failures, and failover issues. For more information, see the AWS Health Dashboard. To request access or discuss your options, submit a support ticket.
You can deploy your instance in the following AWS regions:
| Region | Code | ClickHouse Cloud | AWS SES |
|---|---|---|---|
| Africa (Cape Town) | af-south-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Hyderabad) | ap-south-2 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Jakarta) | ap-southeast-3 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Melbourne) | ap-southeast-4 | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No |
| Asia Pacific (Mumbai) | ap-south-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Osaka) | ap-northeast-3 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Seoul) | ap-northeast-2 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Singapore) | ap-southeast-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Sydney) | ap-southeast-2 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Tokyo) | ap-northeast-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Asia Pacific (Hong Kong) | ap-east-1 | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No |
| Canada (Central) | ca-central-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Frankfurt) | eu-central-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Ireland) | eu-west-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Europe (London) | eu-west-2 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Milan) | eu-south-1 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Spain) | eu-south-2 | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No |
| Europe (Paris) | eu-west-3 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Stockholm) | eu-north-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| Europe (Zurich) | eu-central-2 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Israel (Tel Aviv) | il-central-1 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| Middle East (UAE) | me-central-1 | {{< icon name="dash-circle" >}} No | {{< icon name="dash-circle" >}} No |
| Middle East (Bahrain) | me-south-1 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| South America (São Paulo) | sa-east-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| US East (N. Virginia) | us-east-1 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| US East (Ohio) | us-east-2 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
| US West (N. California) | us-west-1 | {{< icon name="dash-circle" >}} No | {{< icon name="check-circle-filled" >}} Yes |
| US West (Oregon) | us-west-2 | {{< icon name="check-circle-filled" >}} Yes | {{< icon name="check-circle-filled" >}} Yes |
If you need a region that is not listed, contact your account representative or GitLab Support.
Advanced analytical features are only available in regions that support ClickHouse Cloud. Check the supported regions table for ClickHouse availability.
What's included:
Limitations:
AWS Simple Email Service (SES) is used to send emails from your GitLab instance. Check the supported regions table for SES availability in each region.
For regions without AWS SES support, you must set up an external SMTP mail service.