@clickzetta/cz-cli-darwin-arm64 0.3.95 → 0.3.100

package/bin/skills/lakehouse-doc-en/references/privacy-policy.md

@@ -0,0 +1,113 @@
+# Singdata Privacy Policy
+
+--: Version 【2024】【08】
+
+^
+
+This Privacy Policy applies to the access and use of the SingdataCloud Website currently located at [www.singdata.com](http://www.singdata.com), and theuse by registered users of the Singdata Lakehouse of Singdata Cloud productsand services (the “**Cloud Services**”) provided by the Singdata Cloudentity listed in Clause 2 of the *Terms of Use* (referred to as “**we**”, “**our**” or “**SingdataCloud**” hereinafter). Terms not defined in this Privacy Policy shall havethe same meaning as in the Terms of Use of the Singdata Lakehouse.
+
+This Privacy Policy sets out howwe collect, use, transfer, retain, secure and disclose your personal dataand/or personal data about your customers or end users that you provide to uspursuant to your use of the Singdata Lakehouse and/or our Cloud Services, aswell as other terms relating to data location. It also describes your choicesregarding use, access and correction of your personal data.
+
+Many of our Cloud Services offeredthrough the Singdata Lakehouse are intended for use by business organisations.If you use your organisation’s email address to register an account andpurchase or use our Cloud Services, the owner of the domain associated withyour organisation’s email address, and/or your organisation, may monitor orcontrol your account with the Singdata Lakehouse and access, process, and/orcontrol your personal data, as well as the contents of your communications andfiles. Your organisation’s use of our Cloud Services may be subject to yourorganisation’s own rules or policies, and you shall direct all privacyenquiries relating to such rules or policies to your organisation’sadministrators. We are not responsible for the privacy or security practices ofyour organisation.
+
+Cloud Services may be used by ourcustomers (i.e. registered users of Singdata Cloud) to develop or host theirown services and products for the customer’s end users. Any informationcollected or handled by Singdata Cloud in such circumstances is processed onbehalf of our customer who controls the collection and use of such information.We do not have a direct relationship with the end users of our customers. Wherethis is the case, end users should direct all privacy enquiries, such as anyrequests to access, correct, amend or delete personal data, to the SingdataCloud customer providing their services or products. We are not responsible forthe privacy or security practices of our customers.
+
+**A. COLLECTION OF PERSONAL DATA**
+
+1\. If you are (i) an individual or(ii) a representative of a business organisation at the time you register tobecome a user of the Singdata Lakehouse and/or purchase Cloud Services, you maybe asked to complete registration forms which require you to provideinformation such as your email address, mobile number, country, preferredlanguage, name, contact address, and screen nickname. You may also provide tous additional optional contact information in your account profile, such asemail address for sub-accounts, and additional contact phone numbers.
+
+2\. We record details of youractivities (including any purchase or use of our product offerings andservices) when you use the Singdata Lakehouse and/or certain Cloud Services forlegal and/or business purposes. If you make purchases or otherwise transactonline through the Singdata Lakehouse, we also collect information related tosuch transactions including, but not limited to, the types and specificationsof the Cloud Services, pricing information, and any trade dispute/complaintrecords.
+
+3\. When you contact our customersupport, sales or other departments, we may record the communications forsecurity and customer services purposes and collect additional information toverify your identity.
+
+4\. If you make online purchasesfor our Cloud Services through the Singdata Lakehouse, you may be required toprovide information related to your payment instrument (such as credit cards),including information about your payment instrument organisation, your paymentinstrument number, the security code, and the expiration date of your paymentinstrument, directly to our payment service provider.
+
+5\. Please note that certaincategories of data are necessary for us to provide the Cloud Services, such asuser name, address, phone number, and email address. These categories will bespecified at the time of collection. In the event that you do not provide anyor sufficient data marked as mandatory, we may not be able to complete theregistration process or provide you with our Cloud Services.
+
+6\. We also record records ofusers’ buying and browsing activities on the Singdata Lakehouse, including butnot limited to Internet Protocol (“IP”) addresses, browsing patterns andpurchasing patterns. In addition, we automatically gather statisticalinformation about our Singdata Lakehouse and visitors to our Singdata Lakehouseincluding, but not limited to, IP addresses, browser software, operatingsystem, software and hardware attributes, pages viewed, number of sessions andunique visitors.
+
+7\. We may from time to timecollect additional information from you (such as copies of identificationdocuments) and obtain information about you from third parties in order tocarry out risk control, fraud prevention and compliance procedures. For example,we may collect payment-related information from third parties and combine itwith information we collect about you for the purpose of fraud prevention andrisk control.
+
+**B. PURPOSES FOR THE COLLECTION,RETENTION, USE, DISCLOSURE AND TRANSFER OF PERSONAL DATA**
+
+We collect, retain, use anddisclose personal data for the following purposes:
+
+1\. processing your registration asa user, providing you with a user ID for our Singdata Lakehouse and maintainingand managing your registration;
+
+2\. providing you with customerservice and responding to your queries, feedback, claims or disputes;
+
+3\. providing the Cloud Services toyou and/or your end users;
+
+4\. processing your purchasesand/or subscriptions on the Singdata Lakehouse;
+
+5\. personalizing our communicationwith you based on your order history, and performing research or statisticalanalysis in order to improve our product offerings and services;
+
+6\. publishing any information youvoluntarily submit (which may include, but is not limited to, a photograph orother personal data you provide) to our Singdata Lakehouse to be published onour Singdata Lakehouse through the publishing tools (such as our discussionforums);
+
+7\. to comply with applicable law,legal process or lawful government request, or in respect of any claims orpotential claims brought against us or our parent companies, shareholders,subsidiaries and affiliates;
+
+8\. performing risk control, legalcompliance and sanctions screening; and
+
+9\. performing screening and checksfor unlawful, fraudulent, deceptive or malicious activities.
+
+Subject to obtaining your specificconsent (or where otherwise permitted by applicable law in your jurisdiction),we may use your name, phone number, residential address, email address and faxnumber (which may incorporate personal data) to provide notices, surveys,product alerts, related communications and other marketing and promotionalmaterials to you relating to goods and services offered by us on our SingdataLakehouse.
+
+**C. DISCLOSURE OF PERSONAL DATA**
+
+1\. We may disclose your personaldata to third party service providers engaged by us to assist with providingyou with our services (including partners providing customer services to you,contacting you regarding promotions products and services, performing riskcontrol, fraud prevention and legal compliance procedures, and conductingpayment processing services) (the “Third Party Service Providers”). These ThirdParty Service Providers may be located in Singapore or outside of Singapore,and are engaged under terms compliant with applicable data protection lawsand/or appropriate duties of confidentiality to us and are only permitted touse your personal data in connection with the purposes specified in Section Babove, and not for their own purposes. These Third-Party Service Providers mayfurther contract some components of the services they provide to us to otherservice providers. These other service providers may also be located inSingapore or outside of Singapore, and are under a duty of confidentiality toour Third Party Service Providers and are only permitted to use your personaldata in connection with the purposes specified in Section B above, and not fortheir own purposes.​
+
+2\. We may provide aggregated oranonymized data to third parties, but when we do so, the information we shareis in a de-identified format that does not personally identify you.
+
+3\. We have established and willestablish relationships with other parties and websites to offer you thebenefit of their products and services. We offer you access to these otherparties and their websites either through the use of hyperlinks to these sitesfrom our Singdata Lakehouse or through offering “co-branded” sites in whichboth we and other parties share the same uniform resource locator, domain nameor pages within a domain name on the Internet. In some cases you may berequired to submit personal data to register or apply for products or servicesprovided by such third parties or co-branded partners. This Privacy Policy doesnot apply to these third party sites or co-branded sites. The privacy policiesof those other parties may differ from ours, and we have no control over theinformation that you submit to those third parties. You should read therelevant privacy policy for those third party sites and co-branded sites beforeresponding to any offers, products or services advertised by those parties.
+
+4\. Our website offers publiclyaccessible community forums. Any information you provide in these areas may beaccessed, read, collected, and used by others anywhere in the world. To requestremoval of your personal data from our community forums, contact us at <service@singdata.com>.
+
+**D. TRANSFER OF PERSONAL DATA**
+
+Your personal data is primarilystored in our secure servers located in Singapore. As part of providing youwith the Cloud Services, we may need to transfer your personal data from yourjurisdiction to other jurisdictions where our service providers operate.Recipients of the data in these jurisdictions may be subject to data privacylaws different from those in your own jurisdiction. Such overseas transfer orprocessing of your personal data may be necessary to process and administeryour customer account and to provide the Cloud Services effectively.
+
+ 
+
+**E. SECURITY MEASURES**
+
+We use commercially reasonableendeavors to protect the personal data that you provide to us. We also employseveral security techniques, including but not limited to the use ofindustry-standard Secure Socket Layer (SSL) encryption for transmission of personaldata in registration information and payment information and the adoption ofidentity, credential and access management measures for transmission of suchpersonal data to prevent security breaches and unauthorized access of personaldata. We limit access to your personal data and other data to people who needaccess to such data for their work.
+
+Nevertheless, no data transmissionover the internet or any wireless network can be guaranteed to be perfectlysecure. As a result, while we try to protect your personal data, we cannotguarantee the security of any personal data you transmit to us and you do so atyour own risk. We cannot and do not guarantee security in connection with youruse of the Singdata Lakehouse and our Cloud Services.
+
+We retain your personal data aslong as you have an account with us, as needed to provide services or productsto you, to resolve disputes, to serve the purpose of research and statisticalanalysis or as required or permitted by applicable laws, such as tax andaccounting laws.
+
+**F. PERIOD OF RETENTION ANDPROCESSING OF PERSONAL DATA**
+
+We retain your personal data forthe purposes described in this Privacy Policy where we have an ongoinglegitimate business need to do so (for example, to provide you with a serviceyou have requested or to comply with applicable legal, tax or accountingrequirements). In certain circumstances, we will need to keep your personaldata for legal reasons after our relationship has ended. The specific retentionperiods depend on the nature of the personal data and why it is collected andprocessed, and the nature of the legal requirement.
+
+When we have no ongoing legitimatebusiness need or legal reason to process your personal data, we will eitherdelete or anonymize it or, if this is not possible, then we will securely storeyour personal data and isolate it from any further processing until deletion ispossible.​
+
+**G. PROCESS AND METHOD OFDESTRUCTION OF PERSONAL DATA**
+
+Singdata Cloud will delete your personal data asdescribed in Section F of this Privacy Policy. When deleting personal data, wewill take standard commercially reasonable measures to make the personal datapractically irrecoverable or irreproducible. The specific manner of deletionwill depend on the data being deleted, how the data was collected and stored,and your interactions with us. Electronic documents or files containingpersonal data will be deleted using a technical method that makes recovery or retrievalof such information practically impossible or renders the data no longerpersonally identifiable. Non-electronic documents or files containing personaldata will be shredded, incinerated, or both.**​**
+
+**H. RIGHT TO ACCESS/CORRECTPERSONAL DATA; CONTACTING US**
+
+You have the right to request access to your personaldata held by us (or on our behalf) and to request correction or deletion ofsuch personal data. Additionally, upon request, we will provide you withinformation about whether we hold your personal data. You may contact us at <service@singdata.com> torequest access, correction or deletion of your personal data. We will respondto your request within a reasonable timeframe. You may also have supplementalrights under applicable law in relation to your personal data. For example, ifyou are an EEA or UK user, you have the right to object to or request therestriction of processing of your personal data, and to request portability ofyour data by contacting us at <service@singdata.com>.
+
+In cases where we act as aprocessor, we have no direct relationship with the individuals whose personaldata we process. An individual who seeks access, or who seeks to correct,amend, or delete inaccurate data should direct their query to Singdata Cloud’sclient (the data controller).
+
+You may receive e-newsletters fromus. If you would like to discontinue receiving this information, you may updateyour email preferences by using the “Unsubscribe” link found in emails we sendto you or at your member profile.
+
+We do not knowingly collectpersonal data of minors (persons under the age of 18). If a minor has providedus with personal data, the parent or guardian may contact us on the minor’sbehalf to request that we cease any further collection, use and/or disclosureof the personal data and delete the personal data we may hold relating to therelevant minor.
+
+**I. COOKIES**
+
+We and our partners use “cookies”and/or similar technologies, such as web beacons and javascript, to storespecific information about you and track your visits to our Singdata Lakehouse.We may also use “cookies” to store specific information about your use ofcertain Cloud Services as part of its features and to facilitate or enhanceyour user experience of the relevant service. A “cookie” is a small amount ofdata that is sent to your browser and stored on your device. A cookie can besent to your device only if you access our Singdata Lakehouse using a device.If you do not de-activate or erase the cookie, each time you use the samedevice to access our Singdata Lakehouse, our web servers will be notified ofyour visit to our Singdata Lakehouse and in turn we may have knowledge of yourvisit and the pattern of your usage.
+
+Generally, we use cookies to identify you and enable usto i) access your registration information so you do not have to re-enter it;ii) gather statistical information about usage by users; iii) research visitingpatterns and help target advertisements based on user interests; iv) assist ourpartners to track user visits to the Singdata Lakehouse and process orders; v)track progress and participation in promotions; and vi) facilitate your use ofany relevant Cloud Services which may involve the use of cookies. We partnerwith third parties to manage our advertising on other sites. Our third partypartners may use cookies and/or similar technologies in order to provide youadvertising based upon your browsing activities and interests.
+
+You can determine if and how acookie will be accepted by configuring the browser which is installed in thecomputer you are using to access the Singdata Lakehouse. If you choose, you canchange those configurations. You may be able to change your browser preferencesor settings to reject all cookies, or choose to consent each time a cookie issent. If you reject all cookies by choosing the cookie-disabling function inyour browser, you may be required to re-enter information on our SingdataLakehouse more often and certain features of our Singdata Lakehouse may beunavailable.
+
+By accessing and using our Singdata Lakehouse and/orCloud Services, and by accepting the cookies, you consent to the storage ofcookies on your devices. You also consent to the access of such cookies by usand by our partners mentioned above.**​**
+
+**J. CHANGES TO THIS PRIVACY POLICY**
+
+Any changes to this Privacy Policy will becommunicated by us posting an amended Privacy Policy on our Singdata Lakehouse.The new Privacy Policy will become immediately effective once posted on the SingdataLakehouse or at a date specified by Singdata Cloud. We may also in ourdiscretion provide notice to you of any changes to the Privacy Policy. If wemake any material changes we will notify you by email (sent to the e-mailaddress specified in your account) or by means of a notice on this websiteprior to the change becoming effective. Any information and/or personal data wehold about you (as described in this Privacy Policy and whether or notcollected prior to or after the amended and restated Policy comes into effect)will be governed by the latest version of our Privacy Policy. We stronglyencourage you to visit the Singdata Lakehouse from time to time to review thePrivacy Policy. Your continued use of the Singdata Lakehouse and/or the CloudServices signifies your acceptance of the changes to the Privacy Policy.
+
+^

package/bin/skills/lakehouse-doc-en/references/private-link-general.md

@@ -0,0 +1,66 @@
+# Private Link Overview
+
+## What is Private Link?
+
+**Private Link** (AWS PrivateLink, Alibaba Cloud Private Link, Tencent Cloud Private Link, etc.) is a secure, private network connection method provided by cloud vendors. It allows different VPCs (Virtual Private Clouds) to interconnect through an internal network without being exposed to the public internet, significantly reducing the security risks of data transmission.
+
+In the **Lakehouse** platform, the application scenarios of Private Link mainly fall into two categories:
+
+**1. User VPC → Lakehouse (Inbound)**
+Within the same region and availability zone of the cloud vendor, access Lakehouse (JDBC gateway, IGS, etc.) services from the user's VPC through the cloud vendor's Private Link service.
+
+:-: ![](.topwrite/assets/Unnamed_Drawing.drawio.png)
+
+For example:
+
+A company has built its business systems (e-commerce platform, settlement system, etc.) on the cloud, and these systems are deployed in its private VPC, not allowing public internet access. This company stores sales transaction data and inventory data in Lakehouse. When creating data visualizations, real-time analysis, and reports, due to internal compliance and security requirements, it cannot access the data in Lakehouse through the public internet.
+
+At this time, the Lakehouse Private Link feature is needed to establish an endpoint for the customer VPC to access Lakehouse. The company's access to Lakehouse is all within its private VPC, using the domain name of the endpoint.
+
+^
+
+**2. Lakehouse → User VPC (Outbound)**
+When it is necessary to connect from Lakehouse (located in Singdata VPC) to user-defined services (such as a self-built MySQL database within the user VPC), Private Link is also used for private network access.
+
+:-: ![](.topwrite/assets/private_link_access_customer.png)
+
+For example:
+A financial company chooses to use Lakehouse for unified data storage and analysis, but its core business database is stored within a private VPC and has strict security policies prohibiting the exposure of database ports to the public internet. Lakehouse needs to read data in real-time for subsequent analysis and risk control model training.
+
+At this time, the customer first needs to establish an endpoint service within the private VPC, and then use the Lakehouse Private Link feature to establish an endpoint from Lakehouse to the customer VPC. After that, all operations to [create data sources](config-datasource.md) in Lakehouse use the domain name and port of this endpoint for configuration.
+
+^
+
+## Preparations and Considerations
+
+1. **Network Interconnection and DNS Configuration**
+
+   * If you need to access the Private Link Endpoint through a custom domain name (CNAME), you need to point the internal DNS resolution to the private IP within the VPC.
+
+2. **Security Group and Port Allowance**
+
+   * When using Lakehouse to access the customer VPC, the services within the customer's private VPC need to allow the relevant internal IP and port of the endpoint service's LB service.
+
+3. **Default Bandwidth Limit**
+
+   * The default bandwidth for the endpoint service provided by Lakehouse is **5 Mbps**;
+   * If there is a need for large data transmission, please contact the Lakehouse support team to increase the bandwidth limit.
+
+4. **Number of Endpoints and Account Control**
+
+   * To prevent abuse or disorderly creation, each cloud vendor account ID can create a maximum of **5 endpoints**; when the limit is exceeded, the Lakehouse platform will issue an alert.
+
+5. **Billing Method**
+
+   * Private Link traffic fees are paid directly by the customer to the cloud vendor and are not measured by Lakehouse.
+
+6. **Multi-Account Scenarios**
+
+   * If the customer has multiple cloud vendor accounts, they need to add each account ID to the whitelist in Lakehouse;
+   * Correspondingly create multiple Private Link Endpoints and manage them separately.
+
+7. **Public Network Blocking (Optional)**
+
+   * If you want to completely block user access to Lakehouse from the public internet after completing the private network connection, you can enable **network access policies** (or cloud vendor network policies) in Lakehouse to only allow connections from the VPC IP range.
+
+^

package/bin/skills/lakehouse-doc-en/references/private_link.md

@@ -0,0 +1 @@
+# PrivateLink Configuration

package/bin/skills/lakehouse-doc-en/references/private_storage_overview.md

@@ -0,0 +1,165 @@
+# Bring Your Own Storage (BYOS)
+
+> **Private Preview**: This feature is currently in private preview. To enable it for your account, please contact your sales representative to request access through the feature gating process.
+
+## 1. Overview
+
+Bring Your Own Storage (BYOS) allows you to use your own cloud object storage as the data storage location for Lakehouse workspaces. With BYOS, you can:
+
+* Configure private storage through the web console without complex technical setup.
+* Store workspace data in object storage buckets managed under your own cloud platform account.
+* Maintain full control over storage costs and storage policies.
+
+## 2. Use Cases
+
+BYOS is designed for the following scenarios:
+
+* **Data Compliance**: Your organization requires data to reside in object storage under your own cloud account to meet regulatory or compliance requirements.
+* **Data Sovereignty**: You need complete control over where data is stored and who can access it.
+* **Hybrid Deployment**: Some workspaces use Lakehouse-managed storage, while others with stricter compliance needs use your own storage.
+
+## 3. Prerequisites
+
+### 3.1 Create a Storage Bucket
+
+Before configuring BYOS, create a storage bucket on your cloud platform that meets the following requirements:
+
+**Required settings**:
+
+| Setting        | Requirement                                                    | Reason                                                                                   |
+| -------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| Region         | Same cloud provider and same region as your Lakehouse instance | Avoids cross-region data transfer fees                                                   |
+| Storage Class  | Standard                                                       | Do not use infrequent access or archive classes, as they incur additional access charges |
+| Access Control | Private (private read/write)                                   | Ensures data security                                                                    |
+| Dedicated Use  | Exclusive to Lakehouse                                         | Do not share the bucket with other applications to avoid data conflicts                  |
+
+**Recommended settings**:
+
+| Setting                | Recommended Value          | Reason                                                                                                                                             |
+| ---------------------- | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Storage Redundancy     | Choose based on your needs | Locally redundant storage is sufficient for most cases; zone-redundant storage is available for higher availability requirements                   |
+| Versioning             | Disabled                   | Lakehouse manages data versioning internally. Enabling bucket-level versioning may incur additional storage costs                                  |
+| Server-Side Encryption | Disabled                   | Lakehouse handles encryption for specific data based on workspace configuration. Enabling bucket-wide encryption may impact read/write performance |
+| Lifecycle Rules        | Do not configure           | Lakehouse manages file lifecycle internally                                                                                                        |
+
+### 3.2 Create an Access Policy
+
+You must grant the Lakehouse service account full control over your storage bucket (or a dedicated path within it).
+
+**Best practice**: Designate a dedicated bucket — or a specific path prefix within a bucket — exclusively for Lakehouse use, then grant the Lakehouse service account full control permissions on that bucket or path. This ensures clean isolation and avoids permission conflicts with other workloads.
+
+**Getting the Lakehouse Account ID**: The Lakehouse service operates under a cloud-provider-specific account ID in your region. To obtain this account ID, please contact your sales representative or technical support team.
+
+Once you have the Lakehouse account ID, configure the access policy on your cloud platform. The exact steps vary by cloud provider, but the general approach is:
+
+1. Create an IAM or bucket policy that grants the Lakehouse account ID full control over the designated bucket or path.
+
+2. If your cloud provider requires cross-account authorization (e.g., through a role trust relationship), configure the trust policy to allow the Lakehouse account to assume the role.
+
+**Example (AWS)**: Create an S3 bucket policy that grants the Lakehouse account ID `s3:*` permissions on the designated bucket or path prefix, and ensure the IAM trust policy allows the Lakehouse account to assume the role. Other cloud providers follow a similar pattern using their respective IAM and policy mechanisms.
+
+For provider-specific instructions, refer to your cloud provider's documentation on cross-account access or contact the Lakehouse technical support team.
+
+
+## 4. Configuration Steps
+
+### Step 1: Navigate to Private Storage Management
+
+1. Log in to the Lakehouse web console.
+2. Go to **Management** → **More** → **Private Storage**.
+3. Click the + **New** button.
+
+### Step 2: Fill in Storage Information
+
+In the configuration dialog, provide the following details:
+
+1. **Name** (required): Must start with a letter (A-Z, a-z) or underscore (`_`), and be 3–28 characters long. The name must be unique within your Lakehouse service instance. It cannot be changed after creation.
+
+2. **Primary Account ID** (required): Enter your cloud platform account ID. Lakehouse uses this to assume the authorized role and access your bucket. You can find your account ID in your cloud provider's management console, typically under account settings or account information.
+
+
+3. **Bucket Name** (required): Enter the name of your storage bucket. You can optionally include a path prefix. For example:
+   * Bucket only: `my-lakehouse-bucket`
+   * Bucket with path: `my-lakehouse-bucket/data/lakehouse`
+
+4. **Description** (optional): A description of the private storage to help users understand its business purpose and avoid accidental misuse.
+
+After filling in all fields, click **OK** to create the private storage configuration.
+
+> You can create multiple private storage configurations under a single Lakehouse service instance.
+
+### Step 3: Verify Connectivity
+
+After creation, the private storage connection status defaults to **Failed**. You need to verify connectivity:
+
+1. In the private storage list, locate your newly created entry.
+2. Click the **Test Connectivity** button on the right side of the entry.
+
+During the connectivity test, Lakehouse performs the following checks using its service account on the same cloud provider and region:
+
+* Whether the storage bucket exists.
+* Whether the bucket is in the correct region.
+* Whether the access permissions are configured correctly.
+
+Once verification passes, the connection status changes to **Success**.
+
+> If the test fails, double-check your bucket name, region, account ID, and access policy configuration.
+
+### Step 4: Associate with a Workspace
+
+You can associate a private storage location with a workspace only during workspace creation:
+
+1. When creating a new workspace, click to expand the **Advanced Settings** section.
+2. Enable the **Private Storage** toggle.
+3. Select an existing private storage configuration from the dropdown list.
+4. Click **OK** to complete workspace creation.
+
+Key points:
+
+* A single private storage configuration can be associated with multiple workspaces.
+* Data from different workspaces is stored under separate sub-paths within the same bucket, so workspaces do not interfere with each other.
+
+## 5. Important Limitations
+
+### 5.1 Functional Limitations
+
+* A workspace's storage location cannot be changed after creation.
+* A private storage configuration cannot be deleted while it is still associated with any workspace. You must delete the workspace first.
+
+### 5.2 Region Limitations
+
+* Only storage buckets in the same cloud provider and same region as your Lakehouse instance are supported.
+* For AWS environments, ensure the bucket is in the same availability zone to avoid cross-zone traffic charges.
+
+### 5.3 Responsibility Boundaries
+
+* When using BYOS, you are responsible for the availability and reliability of the storage bucket referenced by the private storage configuration.
+* Any data issues not caused by Lakehouse operations are your responsibility.
+
+### 5.4 Billing
+
+When using BYOS:
+
+* Lakehouse does not charge storage capacity fees for data in your private storage. Standard billing continues for any data in Lakehouse-managed storage locations.
+* You pay your cloud provider directly for:
+  * Storage capacity
+  * API access fees
+  * Public network egress fees (if applicable)
+* Logs and temporary files generated by Lakehouse will consume space in your storage bucket.
+
+### 5.5 Performance Considerations
+
+* Storage performance directly affects Lakehouse query and processing efficiency.
+* Ensure your storage service meets the required QPS (queries per second) and bandwidth for your workload.
+* Avoid sharing the bucket with other applications that may compete for storage I/O resources.
+
+## 6. FAQ
+
+**Q1: Can I migrate an existing workspace to BYOS**?
+No. A workspace's storage location is fixed at creation time and cannot be changed afterward.
+
+**Q2: Can one storage bucket be used by multiple workspaces**?
+Yes. A single BYOS configuration can be associated with multiple workspaces. However, plan your bucket usage carefully based on your actual needs.
+
+**Q3: After enabling BYOS, what data does Lakehouse still store in my bucket**?
+Query cache, temporary files, and other operational data will be stored in your bucket and will consume some storage capacity.

package/bin/skills/lakehouse-doc-en/references/product-trial-agreement.md

@@ -0,0 +1,93 @@
+# Product Trial Agreement
+
+## 1. Service Description
+
+1.1 This service (hereinafter referred to as "Service") is a product testing experience provided by \[SINGDATA CLOUD PTE. LTD.] (hereinafter referred to as "Company"). The user understands and agrees that this service is currently in the testing phase, for experience use only, and not as an official commercial version.
+
+1.2 The company provides vouchers to users for experiencing product functions during the testing phase. Users agree to use these vouchers solely for product testing purposes.
+
+ 
+
+## 2. User Responsibilities
+
+2.1 Legal Use: Users commit to using the service legally and not for any illegal or unauthorized purposes. Users must comply with all applicable laws, regulations, and relevant company policies.
+
+2.2 Confidentiality Obligation: Users agree to keep any non-public information about the product (including but not limited to product features, performance data, technical details, etc.) obtained during the use of the service strictly confidential and not disclose it to any third party without the company's written permission.
+
+2.3 Account Security: Users are responsible for the security of their account information and passwords. Users bear responsibility for any loss or unauthorized use of their account due to their own actions. Users should immediately notify the company of any unauthorized use of their account.
+
+2.4 Information Accuracy: Users guarantee that all information provided during registration and use of the service is true, accurate, complete, and up-to-date. Users should promptly update any relevant information if there are changes.
+
+2.5 No Service Abuse: Users must not interfere with or disrupt the normal operation of the service in any way, including but not limited to using automated programs, malicious software, or other tools that may affect service stability.
+
+2.7 Users are fully responsible for any content they generate, publish, or disseminate during the use of the service, ensuring that the content does not contain illegal, threatening, abusive, defamatory, obscene, or rights-infringing information.
+
+2.8 If the company faces any claims or legal proceedings due to the user's use of the service, the user should actively cooperate with the company in investigation and response.
+
+2.9 Users must not transfer their account or rights in the service to any third party.
+
+2.10 Users must comply with all service usage rules set by the company, including but not limited to voucher usage rules, testing process regulations, and senior experience officer rules.
+
+2.11 Users are responsible for backing up important data themselves. The company is not responsible for any data loss that may occur during the use of the service.
+
+ 
+
+ 
+
+## 3. Company Rights
+
+3.1 The company reserves the right to modify, suspend, or terminate the service at any time without prior notice to users. The company is not responsible for any loss caused by this.
+
+3.2 If the user violates any terms of this agreement, the company has the right to immediately terminate the service to that user and reserves the right to pursue legal responsibility.
+
+3.3 The company has the right to collect and use user behavior data generated during the use of the service to improve service quality and develop new products or services. The company promises to comply with relevant laws and regulations to protect user privacy.
+
+3.4 The company has the right to manage user accounts, including but not limited to suspending, closing, or deleting violating accounts, and requiring users to provide identity verification information.
+
+3.5 The company reserves the right to adjust, revoke, or cancel vouchers at any time, including but not limited to changing the usage conditions, validity period, or value of the vouchers.
+
+3.6 The company has the right to decide whether to provide technical support to users, as well as the method and scope of technical support.
+
+3.7 The company has the right to invite users to participate in product improvement surveys or tests, and users can choose whether to participate voluntarily.
+
+3.8 The company has the right to provide necessary user information or take corresponding measures according to the requirements of laws and regulations or government departments.
+
+ 
+
+## 4. Intellectual Property
+
+4.1 Users understand and agree that all intellectual property rights related to the service (including but not limited to copyrights, patent rights, trademark rights, etc.) belong to the company.
+
+4.2 Prohibition of Copying or Dissemination: Without the company's explicit written permission, users must not copy, modify, disseminate, display, perform, resell, or otherwise use any content or materials related to the service in any form.
+
+4.3 Any feedback, suggestions, or opinions provided by users to the company during the use of the service may be used by the company for free and incorporated into products or services without any obligation to pay the user or assume any responsibility.
+
+ 
+
+## 5. Disclaimer
+
+5.1 Users explicitly understand and agree that this test service is provided "as is" and "as available." The company makes no express or implied warranties regarding the applicability, reliability, accuracy, completeness, or timeliness of the service.
+
+5.2 The company does not guarantee that the service during the testing phase will be uninterrupted, timely, secure, or error-free, nor does it guarantee that defects in the service will be corrected or that the service or the servers providing the service are free of viruses or other harmful components.
+
+5.3 Users understand and accept that due to the special nature and unpredictability of the internet, this service may be affected by various external factors, including but not limited to user reasons, network service quality, social environment, etc., which may lead to service interruptions, data loss, and other unforeseeable risks.
+
+5.4 The company does not guarantee the accuracy, completeness, or reliability of any advice, recommendations, or information obtained by users during the use of the service.
+
+5.5 Users explicitly understand and agree that since this service is in the testing phase, there may be unknown defects or issues. The company is not responsible for any loss caused by such defects or issues.
+
+5.6 The vouchers provided by the company are for testing purposes only and have no cash value. The company reserves the right to adjust or cancel the vouchers at any time and assumes no responsibility.
+
+5.7 Third-Party Service Disclaimer: If this service involves any third-party services or content, the company is not responsible for the availability, accuracy, or reliability of such third-party services or content.
+
+5.8 The company is not responsible for any user behavior or any disputes arising between users due to the use of the service.
+
+5.9 Although the company will take reasonable measures to protect user data, it does not guarantee the absolute security of the data. Users should bear the risks involved in using the service.
+
+5.10 Users should ensure that their use of the service complies with all applicable laws and regulations. The company is not responsible for any user violations of laws and regulations.
+
+### 6. Dispute Resolution
+
+6.1 Applicable Law: The conclusion, execution, interpretation, and resolution of disputes under this agreement shall be governed by the laws of the mainland area of the People's Republic of China.
+
+6.2 In the event of any dispute regarding the content or execution of this agreement, both parties shall endeavor to resolve it amicably through negotiation. If negotiation fails, the dispute shall be submitted to the Beijing Arbitration Commission for arbitration.

package/bin/skills/lakehouse-doc-en/references/product_concept.md

@@ -0,0 +1 @@
+^

package/bin/skills/lakehouse-doc-en/references/put-get.md

@@ -0,0 +1 @@
+^

package/bin/skills/lakehouse-doc-en/references/put_get_volume.md

@@ -0,0 +1,3 @@
+# Upload and Download Data to VOLUME from Local
+
+VOLUME provides commands for uploading data from local using PUT, and downloading data to local using GET. For specific usage, please refer to the [PUT](put.md) / [GET](get.md) commands.