github.com/treeverse/lakefs@v1.24.1-0.20240520134607-95648127bfb0/docs/howto/garbage-collection/managed-gc.md (about)

     1  ---
     2  title: Managed Garbage Collection
     3  description: Reduce the operational overhead of running garbage collection manually.
     4  parent: Garbage Collection
     5  nav_order: 5
     6  grand_parent: How-To
     7  redirect_from:
     8    - /cloud/managed-gc.html
     9  ---
    10  
    11  # Managed Garbage Collection
    12  {: .d-inline-block }
    13  lakeFS Cloud
    14  {: .label .label-green }
    15  
    16  {: .note}
    17  > Managed GC is only available for [lakeFS Cloud]({% link understand/lakefs-cloud.md %}). If you are using the self-managed lakeFS, garbage collection is [available to run manually]({% link howto/garbage-collection/index.md %}).
    18  
    19  ## Benefits of using managed GC
    20  * The quick and safe way to delete your unnecessary objects
    21  * No operational overhead
    22  * SLA for when your objects are deleted
    23  * Support from the Treeverse team
    24  
    25  ## How it works
    26  Similarly to the self-managed lakeFS, managed GC uses [garbage collection rules]({% link howto/garbage-collection/index.md %}) to determine which objects to delete.
    27  However, it uses our super-fast and efficient engine to detect stale objects and branches (depends on your configuration) and prioritize them for deletion.
    28  
    29  ## Setting up
    30  Enable managed GC through the lakeFS Cloud onboarding setup wizard.
    31  This will create additional cloud resources for us to use and have access to delete those objects.