@clickzetta/cz-cli-darwin-x64 0.3.94 → 0.3.96

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

@@ -0,0 +1,151 @@
+## Overview
+
+Lakehouse provides a standard Apache Iceberg Catalog REST API interface, allowing external compute engines (such as Apache Spark) to access and query Iceberg tables stored in Lakehouse data lakes (such as Alibaba Cloud OSS object storage) through a unified REST protocol. This enables flexible selection of different compute engines for data analytics while maintaining unified data storage.
+
+## Core Features
+
+* **Standard Compatibility**: Compatible with the Apache Iceberg REST Catalog specification.
+* **Engine Support**: Supports the Spark compute engine.
+* **Credential Delegation**: Manages storage access permissions through the vended-credentials mode.
+* **Multi-Cloud Support**: Supports Alibaba Cloud OSS (future versions will support AWS S3, Tencent Cloud COS, etc.).
+
+## Usage Restrictions
+
+**Data Type Compatibility**
+
+When accessing Singdata Lakehouse tables through the Spark engine, the following data type restrictions apply:
+
+Currently unsupported data types:
+
+* **Integer Types**: `SMALLINT`, `TINYINT`
+* **Semi-structured Types**: `JSON`
+* **Vector Type**: `VECTOR`
+
+## Quick Start
+
+### Prerequisites
+
+1. Account and password for a Singdata Lakehouse instance.
+
+2. Target compute engine environment: Spark 3.5+.
+
+3. Required dependency packages:
+
+   1. Apache Iceberg library (Scala 2.12 / Spark 3.5.x): `org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.6.1`
+
+   2. Corresponding cloud object storage SDK (e.g., Alibaba Cloud OSS: `com.aliyun.oss:aliyun-sdk-oss:3.18.1`)
+
+### PySpark Integration Example
+
+#### Environment Setup
+
+```Python
+import os
+import base64
+from pyspark.sql import SparkSession
+# Set the SPARK_HOME environment variable (adjust according to the actual installation path)
+os.environ['SPARK_HOME'] = '/path/to/pyspark'
+```
+
+Authentication configuration for connecting to Singdata Lakehouse:
+
+```Python
+# Configure authentication information
+username = "your_username"
+password = "your_password"
+
+# Generate Basic Authentication header
+credentials = f"{username}:{password}"
+encoded_bytes = base64.b64encode(credentials.encode("utf-8"))
+encoded_str = encoded_bytes.decode("utf-8")
+auth_header = f"Basic {encoded_str}"
+```
+
+Create Spark Session:
+
+```Python
+spark = SparkSession.builder \
+    .appName('IcebergCatalogIntegration') \
+    .config("spark.jars.packages", "org.apache.iceberg:iceberg-spark-runtime-3.5_2.12:1.6.1," + "com.aliyun.oss:aliyun-sdk-oss:3.18.1") \
+    .config('spark.sql.extensions', 'org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions') \
+    .config('spark.sql.defaultCatalog', 'clickzetta_catalog') \
+    .config('spark.sql.catalog.clickzetta_catalog', 'org.apache.iceberg.spark.SparkCatalog') \
+    .config('spark.sql.catalog.clickzetta_catalog.type', 'rest') \
+    .config("spark.sql.catalog.clickzetta_catalog.header.instanceName", "your_instance_id") \
+    .config("spark.sql.catalog.clickzetta_catalog.header.Workspace", "your_workspace") \
+    .config('spark.sql.catalog.clickzetta_catalog.uri','https://api.singdata.com/api/v1/catalog/iceberg-rest') \
+    .config("spark.sql.catalog.clickzetta_catalog.header.Authorization", auth_header) \
+    .config("spark.sql.catalog.clickzetta_catalog.io-impl", "org.apache.iceberg.aliyun.oss.OSSFileIO") \
+    .config("spark.sql.catalog.clickzetta_catalog.oss.endpoint", "oss-cn-hangzhou.aliyuncs.com") \
+    .config('spark.sql.catalog.clickzetta_catalog.header.X-Iceberg-Access-Delegation','vended-credentials') \
+    .config("spark.sql.catalog.clickzetta_catalog.default-namespace", "public") \
+    .config("spark.sql.catalog.clickzetta_catalog.metrics-reporter-impl", "org.apache.iceberg.metrics.LoggingMetricsReporter") \
+    .getOrCreate()
+```
+
+Usage Example:
+
+```Python
+# View all namespaces (schemas)
+spark.sql("SHOW NAMESPACES IN clickzetta_catalog").show()
+
+# View tables in a specified namespace
+spark.sql("SHOW TABLES IN clickzetta_catalog.public").show()
+
+# View table structure
+spark.sql("DESCRIBE TABLE clickzetta_catalog.public.your_table").show()
+
+# Query data
+df = spark.sql("SELECT * FROM clickzetta_catalog.public.your_table LIMIT 10")df.show()
+
+# Use the DataFrame API
+table_df = spark.table("clickzetta_catalog.public.your_table")
+table_df.filter("column_name > 100").select("col1", "col2").show()
+```
+
+## Detailed Configuration Parameters
+
+| Parameter                                                           | Description                                                                                                                                          | Example Value                                                                                                                                              | Required? |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
+| Spark and Iceberg Basic Configuration                                                        |                                                                                                                                                           |                                                                                                                                                                  |                  |
+| spark.jars.packages                                                      | Specifies the dependency packages that Spark should automatically download from the Maven Central repository at session startup. This includes the Iceberg Spark runtime and the SDK needed to interact with Alibaba Cloud OSS.                                                                     | org.apache.iceberg\:iceberg-spark-runtime-3.5\_2.12:1.6.1,com.aliyun.oss\:aliyun-sdk-oss:3.18.1                                                                  | Yes                |
+| spark.sql.extensions                                                     | Injects Iceberg extension capabilities into Spark SQL. This enables Spark to parse and execute Iceberg-specific DDL and DML statements (e.g., CREATE TABLE ... USING iceberg).                                             | org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions                                                                                                | Yes                |
+| Lakehouse REST Catalog Core Configuration                                              |                                                                                                                                                           |                                                                                                                                                                  |                  |
+| spark.sql.catalog.clickzetta\_catalog                                    | Fixed value. Registers a new catalog named clickzetta\_catalog and specifies its implementation class as Iceberg's SparkCatalog. This is the entry point for defining an Iceberg Catalog.                                                          | org.apache.iceberg.spark.SparkCatalog                                                                                                                            | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.type                               | Fixed value. Specifies the type of clickzetta\_catalog as rest. This tells Iceberg that the Catalog is a remote service communicating via the REST API.                                                                      | rest                                                                                                                                                             | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.uri                                | The API endpoint address of the REST Catalog service. Spark will send all metadata management requests (such as creating tables, getting table info, etc.) to this URL.                                                                                         | https://{endpoint}/api/v1/catalog/iceberg-rest. For endpoint values, refer to the [documentation](https://www.singdata.com/documents/Supported_Cloud_Platforms).                                    | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.header.instanceName                | A custom HTTP request header sent to the REST Catalog. Used to identify your specific instance to the Singdata service.                                                                                                 | your\_instance\_id (replace with your instance ID)                                                                                                                                  | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.header.Workspace                   | A custom HTTP request header sent to the REST Catalog. Used to specify the workspace to operate in within your Singdata instance.                                                                                            | your\_workspace (replace with your workspace name)                                                                                                                                   | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.header.Authorization               | The authorization token used for API authentication. Typically a Bearer token used to verify client identity. This value should be obtained and passed in a secure manner.                                                                                                 | auth\_header (a variable containing authentication information), e.g.: "Basic VUFUX1RFU1Q6QWJjZDEyMzQ1Ng=="                                                                                                | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.header.X-Iceberg-Access-Delegation | This is a special request header for enabling the Vended Credentials mode. Setting it to vended-credentials indicates that the client (Spark) expects the Catalog service to return temporary security credentials for accessing the underlying storage (OSS). This is a more secure access mode that avoids exposing long-term cloud storage keys on the client side.        | vended-credentials                                                                                                                                               | Yes                |
+| Data Storage (OSS) Configuration                                                            |                                                                                                                                                           |                                                                                                                                                                  |                  |
+| spark.sql.catalog.clickzetta\_catalog.io-impl                            | Specifies the FileIO implementation used to read and write data files (such as Parquet, ORC). Here, OSSFileIO is used to interact with Alibaba Cloud OSS.                                                                                      | org.apache.iceberg.aliyun.oss.OSSFileIO                                                                                                                          | Yes                |
+| spark.sql.catalog.clickzetta\_catalog.oss.endpoint                       | The regional endpoint of Alibaba Cloud Object Storage Service (OSS). The client will access OSS buckets through this address.                                                                                                                | [oss-cn-hangzhou.aliyuncs.com](http://oss-cn-hangzhou.aliyuncs.com) (can be modified according to your OSS bucket region; refer to the [documentation](https://help.aliyun.com/zh/oss/user-guide/regions-and-endpoints)) | Yes                |
+| Optional / Auxiliary Configuration                                                                  |                                                                                                                                                           |                                                                                                                                                                  |                  |
+| spark.sql.defaultCatalog                                                 | Sets the default Catalog for Spark SQL. When set, you do not need to explicitly specify the Catalog name before the table name in SQL queries (e.g., you can use `SELECT * FROM my_table` instead of `SELECT * FROM clickzetta_catalog.public.my_table`). | clickzetta\_catalog                                                                                                                                              | No                |
+| spark.sql.catalog.clickzetta\_catalog.default-namespace                  | Sets the default namespace (or database/Schema) within clickzetta\_catalog. When set, table operations will default to this namespace if no namespace is specified.                                                                        | public                                                                                                                                                           | No (but recommended)          |
+| spark.sql.catalog.clickzetta\_catalog.metrics-reporter-impl              | Configures the reporter implementation for Iceberg metrics. LoggingMetricsReporter outputs operation metrics (such as scan duration, file count, etc.) to the Spark logs, which is useful for debugging and performance analysis.                                                          | org.apache.iceberg.metrics.LoggingMetricsReporter                                                                                                                | No                |
+
+## Troubleshooting
+
+### Common Issues and Solutions
+
+1. **Authentication Failure**
+
+   1. Check that the username and password are correct.
+   2. Verify that the Base64 encoding is correct.
+   3. Verify that the account has the appropriate permissions.
+
+2. **Connection Timeout**
+
+   1. Check the network connection.
+   2. Verify that the API endpoint address is correct.
+   3. Adjust timeout parameters.
+
+3. **Table Does Not Exist**
+
+   1. Confirm that the workspace and namespace settings are correct.
+   2. Use `SHOW TABLES` to verify the table name.
+   3. Check user permissions.
+
+^

package/bin/skills/lakehouse-doc-en/references/Structured_and_semi-structured_data_analysis.md

@@ -0,0 +1,171 @@
+# Analyzing Structured and Semi-Structured Data in VOLUME
+
+### Syntax:
+
+```SQL
+SELECT { <column_name>,... | * } 
+FROM VOLUME <volume_name>(
+    <column_name> <column_type>,
+    ...
+) USING CSV|PARQUET|ORC 
+OPTIONS(
+  FileFormatParams
+) 
+FILES|SUBDIRECTORY|REGEXP <pattern>;
+```
+
+### Parameter Description:
+
+- **column_name**: The name of the column contained in the file. Currently, it does not support automatic recognition of the schema in the file, and must be filled in manually. Required field.
+- **column_type**: The type of the column in the file, which must match the predefined column type in the file. Required field.
+- **FileFormatParams**:
+  - CSV format:
+    - sep: Column separator, default is ",", supports up to 1 character in length, e.g., `'sep'=','`.
+    - compression: Configure file compression format. Supported compression formats include gzip/zstd/zlib. For example: `'compression'='gzip'`.
+    - lineSep: Line separator, default is "\n", supports up to 2 characters in length, e.g., `'lineSep'='$'`.
+    - quote: Set a single character used to escape quote values. Default is double quote "", e.g., `'quote'='"'`.
+    - header: Whether to parse the header, default is false. Boolean type, e.g., `'header'='true'`.
+    - timeZone: Configure the time zone, no default value. Used to specify the time zone of the time format in the file. For example: `'timeZone' = 'Asia/Shanghai'`.
+    - escape: Used to escape quotes in quoted values, default is "\", e.g., `'escape'='\'`.
+  - Parquet, ORC, BSON formats:
+    - None
+
+- **FILES**: Specify files. For example: `files('part-00002.snappy.parquet','part-00003.snappy.parquet')`.
+- **SUBDIRECTORY**: Specify sub-path. For example: `subdirectory 'month=02'`.
+- **REGEXP** <pattern>: Regular expression matching. For example: `regexp 'part-.*.parquet'` matches files with parquet suffix starting with part-. Another example: `regexp 'NYC/YellowTaxiTripRecords/parquet/yellow_tripdata_2022.*.parquet'` matches all parquet suffix files starting with *yellow_tripdata_2022* in the sub-path *NYC/YellowTaxiTripRecords/parquet*.
+
+## Examples:
+
+### Query CSV format files:
+
+#### Data Preparation:
+
+Create a volume object: `hz_csv_volume`, bind to Alibaba Cloud OSS path: `oss://hz-datalake/csv_files/`, the file structure under this path is the CSV files of the Brazilian e-commerce dataset:
+
+```
+-------------oss://hz-datalake/csv_files/ Object storage directory structure ------------------
+-- brazil-ecommerce/olist_customers_dataset.csv
+-- brazil-ecommerce/olist_geolocation_dataset.csv
+...
+```
+
+#### Query Examples:
+
+```
+-- Query file: olist_customers_dataset.csv
+SELECT * FROM VOLUME hz_csv_volume (
+  customer_id STRING,
+  customer_unique_id STRING,
+  customer_zip_code_prefix INT,
+  customer_city STRING,
+  customer_state STRING
+) USING CSV 
+OPTIONS(
+  'header'='true',
+  'sep'=','
+) FILES('brazil-ecommerce/olist_customers_dataset.csv');
+
+-- Query file olist_geolocation_dataset.csv
+SELECT * FROM VOLUME hz_csv_volume (
+  geolocation_zip_code_prefix INT,
+  geolocation_lat DECIMAL(10,8),
+  geolocation_lng DECIMAL(11,8),
+  geolocation_city STRING,
+  geolocation_state STRING
+)USING csv 
+ OPTIONS(
+    'header'='true',
+    'sep'=','
+ ) files('brazil-ecommerce/olist_geolocation_dataset.csv');
+```
+
+#### Import Data into Lakehouse:
+
+You can import data into the cloud appliance Lakehouse internal table through the create table as select method:
+
+```
+create Table olist_customers_dataset as
+select * from volume hz_csv_volume (
+  customer_id STRING,
+  customer_unique_id STRING,
+  customer_zip_code_prefix INT,
+  customer_city STRING,
+  customer_state STRING
+)using csv 
+ options(
+    'header'='true',
+    'sep'=','
+ ) files('brazil-ecommerce/olist_customers_dataset.csv');
+```
+
+### Query Parquet format files:
+
+#### Data Preparation:
+
+Create a volume object: `hz_parquet_volume`, bind to Alibaba Cloud OSS path: `oss://hz-datalake/yellowtrip-partitioned/`, the file structure under this path is the New York taxi dataset and some other miscellaneous parquet format files, the purpose is to show how to use `FILES | SUBDIRECTORY | REGEXP` these file matching options to query the target data files. The organization of the files is:
+
+```
+--------- oss://hz-datalake/yellowtrip-partitioned/ Object storage directory structure ----
+-- month=01/yellow_tripdata_2023-01.parquet
+...
+```
+
+#### Query Examples:
+
+Query 1: Query parquet files of month partition 1-5
+
+```
+select * from volume hz_parquet_volume(
+    ...
+) USING parquet regexp 'month=0[1-5].*.parquet' ;
+```
+
+Query 2: Query files with parquet suffix starting with part-, including complex types:
+
+```
+SELECT * FROM volume hz_parquet_volume( 
+    ...
+) USING parquet regexp 'part-.*.parquet';
+```
+
+Query 3: Use files parameter to include specific files, complex type query:
+
+```
+SELECT id, array_col[0],map_col['Key2'],struct_col.field2 FROM volume hz_parquet_volume( 
+    ...
+) USING parquet files(
+    'part-00002-d87581e8-afdb-49ba-abd4-d8f9f5a37a6e-c000.snappy.parquet',
+    'part-00005-d87581e8-afdb-49ba-abd4-d8f9f5a37a6e-c000.snappy.parquet'
+);
+```
+
+### Query ORC format files:
+
+#### Data Preparation:
+
+Create a volume object: `hz_orc_volume`, bind to Alibaba Cloud OSS path: `oss://hz-datalake/orcfiles/`, the file structure under this path is:
+
+```
+--------- oss://hz-datalake/orcfiles/ Object storage directory structure ----------
+-- t_search_log/dt=20230401/hours=06/part-00000-7342ed8826c5.c000
+...
+```
+
+#### Query Example:
+
+```
+SELECT * FROM volume hz_orc_volume (
+    ...
+) USING orc subdirectory 't_search_log/dt=20230401/hours=06/'
+limit 10;
+```
+
+### Query BSON format files:
+
+```SQL
+-- Query bson files
+SELECT * FROM VOLUME my_external_vol
+(name string, age bigint, city string, interests array<string>)
+using bson
+FILES( 'data.bson');
+```

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

@@ -0,0 +1,78 @@
+# Studio: Lakehouse Development and Management Tool
+
+Lakehouse Studio is a web-based integrated development and management toolset natively provided by Lakehouse, offering a graphical user interface designed to deliver comprehensive one-stop functionalities and an intuitive user experience. After logging into Lakehouse Studio via a browser, users can easily operate various product features on the interface, such as uploading/importing or synchronizing data, developing SQL tasks, scheduling jobs, configuring monitoring alerts, performing task operation, and managing users and permissions. Compared to accessing via JDBC protocol connections or CLI command-line tools, Lakehouse Studio provides richer native features and is more convenient and user-friendly.
+
+> It is strongly recommended to use the latest stable version of Google Chrome for optimal operation of Lakehouse Studio. Other browsers have not undergone the same rigorous compatibility testing procedures as Chrome and may exhibit display inconsistencies or rendering anomalies.
+
+## Main Features
+
+Studio provides users with the following main features:
+
+### Data Synchronization
+
+Users can configure data sources through a visual interface to achieve automatic data synchronization and integration.
+
+![](.topwrite/assets/image_1739968909380.png)
+
+***
+
+### Task Development and Scheduling
+
+Users can write, debug, and schedule data processing tasks in the IDE to automate data processing workflows.
+
+![](.topwrite/assets/image_1739968924947.png)
+
+***
+
+### Task Operations and Maintenance
+
+Users can perform operations such as starting, stopping, pausing, and resuming tasks to ensure the stable operation of data processing workflows.
+
+![](.topwrite/assets/image_1739968943424.png)
+
+***
+
+### Task Monitoring and Alerts
+
+Users can view the running status of tasks in real-time and receive real-time notifications of anomalies by setting alert rules.
+
+![](.topwrite/assets/image_1739968956122.png)
+
+***
+
+### Data Quality Management
+
+Users can evaluate, clean, and repair data to ensure its accuracy and consistency.
+
+![](.topwrite/assets/image_1739968969256.png)
+
+***
+
+### Data Catalog Management
+
+Users can categorize and tag data for easier retrieval and usage.
+
+![](.topwrite/assets/image_1739968982370.png)
+
+***
+
+### Security Management
+
+Users can configure access permissions, audit logs, etc., to ensure the security of data and tasks.
+
+***
+
+### Compute Cluster and Job Management
+
+Users can manage and monitor compute cluster resources to optimize job execution efficiency.
+
+![](.topwrite/assets/image_1739968996130.png)
+![](.topwrite/assets/image_1739969007011.png)
+
+***
+
+### Workspace Management
+
+Users can create and manage multiple workspaces to achieve isolation and collaboration between projects and teams.
+
+![](.topwrite/assets/image_1739969015185.png)

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

@@ -0,0 +1,105 @@
+# Syncing RDS Data Within VPC via Private Link Combined with SSH
+
+## 1. Applicable Scenarios
+
+Lakehouse Studio **Data Integration** syncs RDS data through VPC networks, solving the following problems associated with public network transmission:
+
+* High data latency
+* High public network traffic costs
+* Insecure/non-compliant
+
+## 2. Summary of Previous Solutions' Pros and Cons
+
+* **Pure Private Link Solution**: Does not support connecting to RDS instances; only supports self-managed MySQL on ECS.
+* **VPC Peering Verification Passed**: However, it exposes both sides' internal network environments, posing security risks and is not recommended.
+* **Via IGS SDK**: Supports pushing data to Lakehouse through Private Link, but import scheduling strategies need to be managed by the customer themselves and cannot be integrated into workflows.
+* **Pure SSH TUNNEL**: The intermediate segment requires going through the public network, which can solve the security issue of exposing RDS to the public network, but cannot solve the public network traffic issue.
+
+## 3. Introduction to This Solution
+
+This solution combines Private Link with SSH Tunnel.
+
+Network architecture diagram (using Alibaba Cloud as an example):
+
+![](.topwrite/assets/whiteboard_exported_image.png)
+
+(The customer environment may also be in other availability zones within the same Region)
+
+By default, the **endpoint** side bears the costs. There are two billing items; for details, refer to [Billing Rules](https://help.aliyun.com/document_detail/198081.html?spm=a2c4g.120462.0.0.462f29e3tnGfMO#section-4zx-gat-sg7).
+
+## 4. Configuration Method (Example):
+
+### Step 1: Environment Preparation
+
+**Customer-Side Environment**:
+
+* VPC: Hangzhou H: Virtual Private Cloud **VPC_Customer**: [vpc-bp1qmyayneio4mlyoyeb7](https://vpc.console.aliyun.com/vpc/cn-hangzhou/vpcs/vpc-bp1qmyayneio4mlyoyeb7?type=base), CIDR: `172.16.0.0/12`
+* RDS: Hangzhou H: Private network address: `` (`rm-bp15gq963ic327h8f.mysql.rds.aliyuncs.com`)
+* ECS: Hangzhou H: Private network IP address `172.16.12.182`
+
+**Lakehouse Side**:
+
+Singdata Studio UAT environment data integration EMR cluster VPC and vSwitch: Hangzhou H
+
+| SQL vpc-bp1jvn\*\*\*\*\*\*\*\*\*\*\*u  vsw-bp1rp\*\*\*\*\*\*\*\*\*\*\*\*cii |
+| --------------------------------------------------------------------------- |
+
+Singdata UAT environment Alibaba Cloud primary account: `138************83`
+
+### Step 2: Create SSH Port Forwarding on ECS
+
+In the customer network environment, create an ECS instance that can communicate with RDS. On this machine, create port forwarding: access to port 12345 on this ECS will be forwarded to port 3306 on RDS.
+
+```Shell
+ssh -CfNg -L 12345:rm-bp15gq963ic327h8f.mysql.rds.aliyuncs.com:3306 root@127.0.0.1 -p22
+
+## Verify:
+ps aux | grep ssh
+```
+
+![](.topwrite/assets/c417a0f96d/e4dc75c9ba552ccaca172ab265aeeb5dbc67505e.png)
+
+***
+
+### Step 3: Create Load Balancer CLB
+
+* Enter SLB console -> Left sidebar **Classic Load Balancer (CLB, formerly SLB)** -> **Create Classic Load Balancer**
+
+* Create listener as follows:
+  ![](.topwrite/assets/c417a0f96d/c4ec47d374f0564f96375d460e06a2b096c64688.png)
+
+* In the **Default Server Group** tab, add the ECS from Step 2, with frontend port 22 (custom) and backend port as the port forwarded to RDS, which is 12345 in this case.
+
+### Step 4: Customer Side: Create Endpoint Service
+
+* Enter VPC console, select the same Region as the Singdata data integration cluster, left sidebar **Endpoint Service** -> **Create Endpoint Service**
+* **Service Resource Type -> Classic Load Balancer CLB** (consistent with Step 1), select Availability Zone **Hangzhou Zone H**, choose the CLB instance created in Step 1 from the dropdown, auto-accept endpoint connections: Yes, other settings default
+* Enter this endpoint service: In **Service Whitelist**, add the Singdata environment primary account: `1384322691904283`
+
+  ![](.topwrite/assets/c417a0f96d/fc469bdcdf20cda3bca8b56dfa9d4b66b010e090.png)
+
+### Step 5: Lakehouse Side Create Endpoint
+
+* Enter VPC console, select the same Region as the Singdata data integration cluster, select **Endpoint** in the left menu.
+* On the Endpoint page, the system will automatically discover the endpoint service created in Step 4. After selecting the corresponding **VPC**, confirm creation;
+* In the **Endpoint Service** and **Endpoint** connection information on both the customer side and Lakehouse side, you can obtain the domain name.
+
+### **Verification**:
+
+**Lakehouse Studio Data Integration**:
+
+In the data source configuration, use the following JDBC URL: `jdbc:mysql://ep-bp1iabb21a27719ca8a2-cn-hangzhou-h.epsrv-bp1n7rvc8qbpudxk69fr.cn-hangzhou.privatelink.aliyuncs.com:22/mysql`
+
+![](.topwrite/assets/c417a0f96d/edb20aeb52d76a06e65943c74983bd38b00dac5e.jpeg)
+
+The CLB listener port bound to the endpoint service is 22, and the backend ECS resource port is 12345;
+
+![](.topwrite/assets/c417a0f96d/d0297891972911f184c690e7585cff01aaa5943f.jpeg)
+
+MySQL console:
+
+![](.topwrite/assets/c417a0f96d/3b17582b28ae004533c8998acf76c2a7cee76bc5.jpeg)
+
+Data Integration verification: Import successful
+
+![](.topwrite/assets/20240520-211021.jpeg)

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

@@ -0,0 +1,34 @@
+# Cloud Services and Region Support
+
+## Region Support
+
+Singdata Lakehouse, as a SaaS-based data management and analysis service, fully leverages cloud infrastructure to provide users with an efficient and convenient service experience. We are committed to meeting the data integration and connectivity needs of customers and business systems across different cloud service providers and regions.
+
+Currently, Singdata Lakehouse is available in the following cloud service providers and regions, with plans to expand further:
+
+| Cloud Service Provider | Region    | Region Code             |
+| ---------------------- | --------- | ----------------------- |
+| Alibaba Cloud          | Singapore | ap-southeast-1-alicloud |
+| Amazon Web Services    | Singapore | ap-southeast-1-aws      |
+
+## Service Domain Names
+
+When you register a Singdata Lakehouse account, the system will automatically assign a unique account name. You will need to use this account name to log in to the account center for account management. In the account center, administrators can enable and create Lakehouse service instances for you in the specified cloud service provider and region. Please note that the Lakehouse service instance name is globally unique.
+
+| Service                      | Sub-service                | Domain Name                                                              |
+| ---------------------------- | -------------------------- | ------------------------------------------------------------------------ |
+| Account Console              | Account Management Center  | accounts.app.singdata.com&#xA;\<account\_name>.accounts.app.singdata.com |
+| Account Console              | Account Management Center  | accounts.singdata.com&#xA;\<account\_name>.accounts.singdata.com         |
+| Product Web Console          | Lakehouse Instance Console | \<instance\_name>.app.singdata.com                                       |
+|                              | Lakehouse Workspace List   | \<instance\_name>.app.lakehouse.singdata.com/workspace                   |
+| Lakehouse JDBC URL           |                            | jdbc\:clickzetta://\<instance\_name>.\<region\_code>.api.singdata.com/   |
+| Lakehouse Streaming API Host |                            | \<instance\_name>.streamingapi.singdata.com                              |
+
+**JDBC Domain Names**
+
+| Cloud Service Provider | Region    | Region Code             | Domain Name                                                                    |
+| ---------------------- | --------- | ----------------------- | ------------------------------------------------------------------------------ |
+| Alibaba Cloud          | Singapore | ap-southeast-1-alicloud | jdbc\:clickzetta://\<instance\_name>.ap-southeast-1-alicloud.api.singdata.com/ |
+| Amazon Web Services    | Singapore | ap-southeast-1-aws      | jdbc\:clickzetta://\<instance\_name>.ap-southeast-1-aws.api.singdata.com/      |
+
+Note: For the creation and acquisition of account name \<account\_name> and instance name \<instance\_name>, please refer to [logging in](logging-in.md).