Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
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
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Stopping a instance
  • Starting a instance
  1. Step-by-step guides
  2. Stopping and starting an instance

Stopping and starting a GitLab instance

Written by
Yandex Cloud
Updated at July 15, 2025
  • Stopping a instance
  • Starting a instance

If necessary, you can stop and restart a GitLab instance. When the instance is stopped, all its data is saved.

You are not charged while your instance is stopped: you continue to pay only for the data stored by the instance and the size of backups stored in Yandex Object Storage based on the pricing policy.

Stopping a instanceStopping a instance

Management console
CLI
API
  1. Navigate to the folder dashboard and select Managed Service for GitLab.
  2. Find the instance in the list, click , and select Stop.
  3. In the dialog box that opens, confirm that you want to stop the instance, then click Stop.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To stop a GitLab instance, run this command:

yc managed-gitlab instance stop <instance_name_or_ID>

You can request the instance ID or name with the list of instances in the folder.

Result:

done (20s)
id: c17ab1ehdfag********
folder_id: b1gmm82dtdb3********
created_at: "2024-01-29T16:11:45.859Z"
updated_at: "2025-06-25T20:38:41.325Z"
name: inst-gitlab
resource_preset_id: s2.micro
disk_size: "32212254720"
status: STOPPED
admin_login: <admin_login>
admin_email: <email>
domain: example.gitlab.yandexcloud.net
subnet_id: e9bp8qmchqh2********
backup_retain_period_days: "7"
approval_rules_id: NONE
gitlab_version: 17.11.4

For more information about this command, see the CLI reference.

Use the Stop REST API method for the Instance resource or the InstanceService/Stop gRPC API call.

Starting a instanceStarting a instance

You can restart your Stopped instance.

Management console
CLI
API
  1. Navigate to the folder dashboard and select Managed Service for GitLab.
  2. Find the stopped instance in the list, click , and select Start.
  3. In the dialog box that opens, confirm that you want to start the instance by clicking Start.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To start a GitLab instance, run this command:

yc managed-gitlab instance start <instance_name_or_ID>

You can request the instance ID or name with the list of instances in the folder.

Result:

done (1m44s)
id: c17ab1ehdfag********
folder_id: b1gmm82dtdb3********
created_at: "2024-01-29T16:11:45.859Z"
updated_at: "2025-06-25T20:38:41.325Z"
name: inst-gitlab
resource_preset_id: s2.micro
disk_size: "32212254720"
status: RUNNING
admin_login: <admin_login>
admin_email: <email>
domain: example.gitlab.yandexcloud.net
subnet_id: e9bp8qmchqh2********
backup_retain_period_days: "7"
approval_rules_id: NONE
gitlab_version: 17.11.4

For more information about this command, see the CLI reference.

Use the Start REST API method for the Instance resource or the InstanceService/Start gRPC API call.

Was the article helpful?

Previous
Setting up security groups and access restrictions to an instance
Next
Editing instance settings
© 2025 Direct Cursus Technology L.L.C.