Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for GitLab
  • Getting started
    • All guides
    • Getting instance info
    • Creating and activating an instance
    • Configuring security groups
    • Stopping and starting an instance
    • Updating instance settings
    • Managing backups
    • Migrating from a custom GitLab installation
    • Migrating to a different availability zone
    • Cleaning up full disk space
    • Deleting an instance
    • Creating and adding users to a project
    • Setting up approval rules
    • Instance state monitoring
    • Setting up OmniAuth
    • Integration with Object Storage
    • Working with a managed runner
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

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

Stopping and starting a GitLab instance

Written by
Yandex Cloud
Updated at August 5, 2026
View in Markdown
  • Stopping an instance
  • Starting an instance

You can stop and restart a GitLab instance as needed. When stopped, an instance retains all its data.

While your instance is idle, you only pay for the stored instance data and the size of backups stored in Yandex Object Storage as per the pricing policy.

Stopping an instanceStopping an instance

Management console
CLI
API
  1. Navigate to 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 by clicking Stop.

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

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To stop a GitLab instance, run this command:

yc managed-gitlab instance stop <instance_name_or_ID>

You can get 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_address>
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 an instanceStarting an instance

You can restart Stopped instances.

Management console
CLI
API
  1. Navigate to 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 yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

To start a GitLab instance, run this command:

yc managed-gitlab instance start <instance_name_or_ID>

You can get 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_address>
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
Configuring security groups
Next
Updating instance settings
© 2026 Direct Cursus Technology L.L.C.