[Yandex Cloud documentation](../../index.md) > [Yandex Managed Service for GitLab](../index.md) > [Concepts](index.md) > Integration with Object Storage

# 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](index.md#instance) disks to prevent their overflow. For more information, see [this GitLab article](https://docs.gitlab.com/administration/object_storage/).

In Managed Service for GitLab, you can [enable integration with an S3-compatible Object Storage](../operations/objstorage-integration.md) using the [management console](https://console.yandex.cloud). In which case Managed Service for GitLab will manage the storage creation, usage, and scaling.

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](https://git-lfs.com/).
* `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.

{% note 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.

{% endnote %}