github.com/treeverse/lakefs@v1.24.1-0.20240520134607-95648127bfb0/docs/understand/lakefs-cloud.md (about)

     1  ---
     2  title: lakeFS Cloud
     3  description: lakeFS Cloud is a fully-managed lakeFS solution
     4  parent: Understanding lakeFS
     5  redirect_from: 
     6      - /cloud.html
     7      - /cloud/index.html
     8  ---
     9  
    10  # lakeFS Cloud
    11  
    12  [lakeFS Cloud](https://lakefs.cloud) is a fully-managed lakeFS solution provided by Treeverse, implemented using our best practices, providing high availability, auto-scaling, support and enterprise-ready features.
    13  	
    14  ## lakeFS Cloud Features
    15  * [Role-Based Access Control]({% link reference/security/rbac.md %})
    16  * [Auditing]({% link reference/auditing.md %})
    17  * [Single-Sign-On]({% link reference/security/sso.md %}#sso-for-lakefs-cloud) (including support for SAML, OIDC, AD FS, Okta, and Azure AD)
    18  * [Managed Garbage Collection]({% link howto/garbage-collection/managed-gc.md %})
    19  * [Private-Link]({% link howto/private-link.md %})
    20  * [Transactional Mirroring]({% link howto/mirroring.md %})
    21  * SOC 2 Type II Compliance
    22  
    23  ## How lakeFS Cloud interacts with your infrastructure
    24  
    25  Treeverse hosts and manages a dedicated lakeFS instance that interfaces with data held in your object store, such as S3. 
    26  
    27  ```mermaid
    28  flowchart TD
    29      U[Users] --> LFC
    30  
    31      subgraph Your Infrastructure
    32      IAMM[lakeFS Managed GC IAM Role] --> ObjectStore[Client's Object Store]
    33      IAMA[lakeFS Application IAM Role] --> ObjectStore
    34      end
    35  
    36      subgraph Treeverse's Infrastructure
    37      MGC[Managed Garbage Collection] --> EMR[Elastic Map Reduce]
    38      EMR --> IAMM
    39      MGC --> CP
    40      CP[Control Plane]
    41      LFC --> CP
    42  
    43          subgraph Client's Tenant
    44          LFC[lakeFS Cloud] --> DB[Refstore Database]
    45          end
    46          
    47      LFC --> IAMC[lakeFS Connector IAM Role]    
    48      IAMC -->|ExternalID| IAMA
    49      end
    50  ```
    51  
    52  ## Setting up lakeFS Cloud
    53  
    54  ### AWS / Azure
    55  Please follow the self-service setup wizard on [lakeFS Cloud](https://lakefs.cloud)
    56  
    57  ### GCP
    58  Please [contact us](mailto:support@treeverse.io) for onboarding instructions.
    59  
    60  ## Scalability Model
    61  
    62  By default, a lakeFS Cloud installation supports:
    63  - 1,500 read operations/second across all branches on all repositories within a region
    64  - 1,500 write operations per second across all branches on all repositories within a region
    65  
    66  This limit can be increased by contacting [support](mailto:support@treeverse.io?subject=quota+increase). 
    67  
    68  Each lakeFS branch can sustain up to a maximum of 1,000 write operations/second and 3,000 read operations per second. 
    69  This scales horizontally, so for example, with 10 concurrent branches, a repository could sustain 10k writes/second and 30k reads/second, assuming load is distributed evenly between them.
    70  
    71  Reading committed data (e.g. from a commit ID or tag) could be scaled up horizontally to any desired capacity, and defaults to ~5,000 reads/second.
    72