Integration with Yandex Object Storage
GitLab supports storing various types of data in an S3 storage. Integration with an S3 storage allows you to reduce the amount of data on instance disks to prevent their overflow. Learn more about data storage in this GitLab guide.
In Managed Service for GitLab, you can enable integration with an S3-compatible Object Storage using the management console. In which case Managed Service for GitLab will manage the storage creation, usage, and scaling.
Specifics and limitations
Enabling integration with Object Storage will reconfigure the instance. If you need to reissue your Let's Encrypt® certificate at this point, the reconfiguration will run an HTTP-01 Challenge check and Let's Encrypt® will connect to your domain on port 80. If the security group is blocking traffic on this port, the certificate will not be renewed, the reconfiguration will fail, and the data migration will not start. Therefore, before enabling integration with Object Storage, make sure the security group of the Managed Service for GitLab instance allows incoming connections on port 80 from external IP addresses of Let's Encrypt®.
Alert
If you disable data storage in Object Storage, your instance will lose access to the existing data. Reverse migration to the GitLab local storage is not supported. New data will be saved to the GitLab local storage.
Data types available for storage
You can select data types to store in Object Storage:
Artifacts: Archives of job files and folders.External diff files: Files with version diffs in merge requests.Attached files: User files.Git LFS: Large file storage.Packages: Package registry.Dependency proxy: Dependency cache.Terraform states: Terraform state files.GitLab Pages: Websites.Protected CI files: Restricted access files.Container Registry: Container images.
Migrating files from large repositories to Object Storage can take more than a day.