Create an AnalyticDB for MySQL Data Lakehouse Edition cluster - AnalyticDB

This topic describes how to create a Data Lakehouse Edition cluster in the AnalyticDB for MySQL console.

Procedure

Log on to the AnalyticDB for MySQL console. In the upper-right corner of the console, click Buy Cluster.
Select an option for the Product Type parameter.
- Pay-as-you-go: You are charged on an hourly basis for the resources that you use. This billing method is suitable for short-term usage. To reduce costs, you can release pay-as-you-go clusters when they are no longer needed.
- Subscription: You must pay an upfront subscription fee when you create subscription clusters. For long-term usage, this billing method is more cost-effective than the pay-as-you-go billing method. You are charged lower prices for longer subscription periods.

Configure the parameters that are described in the following table and click Buy Now in the lower-right corner of the page.

Parameter	Description
Edition	The edition of the cluster. Select Data Lakehouse Edition.
Region	The region in which you want to create the cluster. After a cluster is created, you cannot change the region of the cluster. To maximize the cluster access speed, we recommend that you select a region that is geographically closest to your business.
Zone	The zone in which you want to create the cluster. Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences.
Service-linked Role	The AliyunServiceRoleForAnalyticDBForMySQL role that allows AnalyticDB for MySQL to create cluster-related resources.
VPC vSwitch	If you have created a virtual private cloud (VPC) that meets your business requirements, you can select the VPC. For example, if you have created an Elastic Compute Service (ECS) instance in a VPC that meets your business requirements, select the VPC. If you have not created a VPC that meets your business requirements, you can use the default VPC and vSwitch. For more information, see Default VPCs and default vSwitches. If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPCs and vSwitches. For more information, see Create and manage a VPC. Important If you use other Alibaba Cloud services such as ECS and ApsaraDB RDS, make sure that your AnalyticDB for MySQL cluster resides in the same VPC as your ECS and ApsaraDB RDS instances. If your cluster and instances reside in different VPCs, your cluster cannot communicate with your instances over an internal network to achieve optimal performance.
Activate PrivateLink	PrivateLink provides private connectivity between VPCs, which ensures secure and efficient access to AnalyticDB for MySQL and prevents potential security risks caused by public connections. You can create clusters only after you activate PrivateLink. Each Alibaba Cloud account needs to activate PrivateLink only once. You are not charged for the activation of PrivateLink. Note If you are not prompted to activate PrivateLink, PrivateLink has been activated and you do not need to select the check box.
Time Zone	The time zone in which you want to create the cluster. After you select a time zone, the system performs time-related data writes based on the selected time zone. By default, UTC+8 is used.
Reserved Computing Resources	The reserved computing resources of the cluster. You can use reserved computing resources to compute data. The increase in the computing resources can accelerate data queries. If you want to create AnalyticDB for MySQL internal tables, make sure that the amount of reserved computing resources is greater than 0 ACUs. If the amount of reserved computing resources is 0 ACUs, you can use only external tables. If you select 0 ACUs of reserved computing resources when you create a cluster, you can purchase reserved computing resources later by scaling up the cluster. For more information, see Scale a Data Lakehouse Edition cluster.
Default Allocation Behavior	Specifies whether to allocate all reserved computing resources to the user_default resource group. After you create a cluster, you can modify the amount of reserved computing resources for the user_default resource group on the Resource Management page. Valid values: Yes: All reserved computing resources are allocated to the user_default resource group. You can use the user_default resource group to create tables, write data, and query data. No: No reserved computing resources are allocated to the user_default resource group. You cannot use the resource group to create tables, write data, or query data. You must allocate resources to the resource group or create other resource groups.
Load Built-in Dataset	Specifies whether to automatically load a built-in dataset after the cluster is created. Valid values: Yes: A built-in dataset is automatically loaded after the cluster is created. No: No built-in dataset is automatically loaded after the cluster is created. You can manually load a built-in dataset based on your business requirements. For more information, see the "Manually load a built-in dataset" section of the Manage a built-in dataset topic. Note This parameter is supported only when the Default Allocation Behavior parameter is set to Yes. A built-in dataset is approximately 10 GB in size. You are not charged for the storage that is occupied by the built-in dataset.
Reserved Storage Resources	The reserved storage resources of the cluster. You can use reserved storage resources to store hot data. A set of reserved storage resources is equal to 24 ACUs and can store up to 8 TB of hot data. Important If you set the Reserved Computing Resources parameter to 0 ACUs, you must set the Reserved Storage Resources parameter to 0 ACUs. If you cannot determine the amount of required reserved storage resources when you create a cluster, you can set the Reserved Storage Resources parameter to 0 ACUs, and then purchase reserved storage resources by scaling up the cluster based on your business requirements. For more information, see Scale a Data Lakehouse Edition cluster. You are billed for hot data storage based on the actual storage usage. For more information, see Billable items of Data Lakehouse Edition.
Version Update Policy	The policy that is used to update the cluster version. The cluster is automatically updated to the latest version within a specific maintenance window. The default maintenance window is from 12:00 to 13:00. After you create a cluster, you can modify the maintenance window for the cluster. For more information, see Configure a maintenance window.

Note

After you create a cluster, you can purchase ACU-hour plans that contain a specific number of ACU-hours at lower costs to offset the amount of pay-as-you-go ACU resources. For more information, see ACU-hour plans.
You can purchase storage plans that contain a specific amount of storage resources at lower costs to offset the amount of pay-as-you-go hot and cold data storage. For more information, see Storage plans.