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 ProviderRegionRegion Code
Alibaba CloudSingaporeap-southeast-1-alicloud
Amazon Web ServicesSingaporeap-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.

ServiceSub-serviceDomain Name
Account ConsoleAccount Management Centeraccounts.app.singdata.com <account_name>.accounts.app.singdata.com
Account ConsoleAccount Management Centeraccounts.singdata.com <account_name>.accounts.singdata.com
Product Web ConsoleLakehouse Instance Console<instance_name>.app.singdata.com
Lakehouse Workspace List<instance_name>.app.lakehouse.singdata.com/workspace
Lakehouse JDBC URLjdbc:clickzetta://<instance_name>.<region_code>.api.singdata.com/
Lakehouse Streaming API Host<instance_name>.streamingapi.singdata.com

JDBC Domain Names

Cloud Service ProviderRegionRegion CodeDomain Name
Alibaba CloudSingaporeap-southeast-1-alicloudjdbc:clickzetta://<instance_name>.ap-southeast-1-alicloud.api.singdata.com/
Amazon Web ServicesSingaporeap-southeast-1-awsjdbc: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.