Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for GitLab
  • Getting started
    • All guides
    • Getting information about instances
    • Creating and activating an instance
    • Setting up security groups and access restrictions to an instance
    • Stopping and starting an instance
    • Editing instance settings
    • Managing backups
    • Migrating from a custom GitLab installation
    • Migrating to a different availability zone
    • Cleaning up full disk space
    • Deleting an instance
    • Adding and removing users from a project
    • Setting up approval rules
    • Monitoring the instance status
    • Setting up OmniAuth
  • Access management
  • Pricing policy
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Migrating to a different availability zone

Migrating an instance to a different availability zone

Written by
Yandex Cloud
Updated at March 6, 2025

Note

This feature is at the Preview stage and is available upon request.

VMs with Managed Service for GitLab instances reside in Yandex Cloud availability zones. To change the availability zone:

  1. If you do not have a subnet in the target availability zone, create one.

  2. If the instance's security group is set up for a subnet in the source availability zone, recongifure the group for the new subnet. To do so, replace the source subnet CIDR with the new subnet CIDR in the security group rules.

  3. Change the instance's availability zone:

    Management console
    1. In the management console, go to the folder page and select Managed Service for GitLab.

    2. Click the instance name and select the Migration tab.

    3. If unable to use the migration functionality, request access to it.

      When your request is approved, you will be notified by email. To continue, reload the page in your browser.

    4. Specify the target availability zone and subnet.

    5. Click Move instance.

      The instance will start to upgrade. Wait for the instance to change its status back to Running. This will take a few minutes for a small instance or at least 30 minutes if the instance is over 200 GB in size. After a few more minutes, the GitLab instance will start.

    6. To test the instance's performance, select the Overview tab and click the link in the Domain field.

    7. On the Migration tab:

      • If the instance works properly, click Complete migration.
      • If the instance is inoperable, click Cancel migration to move it back to the initial availability zone or contact support.

Was the article helpful?

Previous
Migrating from a custom GitLab installation
Next
Cleaning up full disk space
Yandex project
© 2025 Yandex.Cloud LLC