AnalyticDB:Create a cluster

1. Log on to the AnalyticDB for MySQL console. In the upper-right corner of the console, click Buy Cluster.

2. 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.

3. 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 Enterprise Edition (Multi-replica) or Basic Edition (Single-replica). Enterprise Edition runs in multi-replica mode and uses a multi-replica storage architecture. Enterprise Edition provides distributed capabilities and high availability. Basic Edition runs in single-replica mode and uses a single-replica storage architecture. Basic Edition does not provide high availability. For more information about Enterprise Edition and Basic Edition, see Editions.
   Deployment Mode	Enterprise Edition: You can select Single-zone Deployment or Multi-zone Deployment. Important Multi-zone deployment is supported only by the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Hong Kong), and Singapore. Basic Edition: This parameter is automatically set to Single-zone Deployment.
   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.
   Primary Zone	The primary zone of the cluster.
   Secondary Zone	The secondary zone of the cluster. If the primary zone fails, the cluster workloads are automatically switched to the secondary zone. During the switchover, a read/write failure or timeout error may occur on the cluster. Important You must specify this parameter only if you set the Deployment Mode parameter to Multi-zone Deployment.
   Service-linked Role	The AliyunServiceRoleForAnalyticDBForMySQL role that allows AnalyticDB for MySQL to create cluster-related resources.
   VPC vSwitch of Primary Zone vSwitch of Secondary Zone	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. You must specify the vSwitch of Secondary Zone parameter only if you set the Deployment Mode parameter to Multi-zone Deployment.
   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.
   Single-node Specifications of Reserved Resources	The single-node specifications of reserved resources. Default value: 8 AnalyticDB compute units (ACUs). Reserved resources can be used for the following purposes: Data computing. An increase in the reserved resources can accelerate data queries. Hot data storage. A set of reserved resources can store up to 8 TB of hot data. You are billed for hot data storage based on the actual storage usage. Note If you have purchased Data Warehouse Edition or Data Lakehouse Edition clusters, you can select specifications for Enterprise Edition clusters based on their specification mappings. For more information, see the "Specification mappings between Data Warehouse Edition, Data Lakehouse Edition, and Enterprise Edition" section of this topic.
   Reserved Resource Nodes	The number of reserved resource nodes in an Enterprise Edition cluster. Default value: 3. Step size: 3. Note When you create an Enterprise Edition cluster, you can set the number of reserved resource nodes to 0. In this case, the price for the number of reserved resource nodes is not displayed in the lower-right corner of the buy page. Take note of the following items: If the number of reserved resource nodes is 0, you can use only external tables. If you want to create AnalyticDB for MySQL internal tables, make sure that the number of reserved resource nodes is greater than 0. If you set the number of reserved resource nodes to 0 when you create a cluster, you can purchase reserved resources later by scaling up the cluster. For more information, see Scale an Enterprise Edition or Basic Edition cluster. The number of reserved resource nodes in a Basic Edition cluster. Default value: 1. Step size: 1.
   Disk Encryption	If you select Disk Encryption, the system encrypts data on each data disk of your cluster based on block storage. This way, your data cannot be decrypted even if the data is leaked. The first time you use the disk encryption feature, select Disk Encryption and click Create Service-linked Role to create a service-linked role. Then, select a key from the Key drop-down list. For more information, see Disk encryption. Important You can enable the disk encryption feature for an AnalyticDB for MySQL cluster only when you create the cluster. After you create an AnalyticDB for MySQL cluster, you cannot enable or disable the disk encryption feature for the cluster. The disk encryption feature requires Key Management Service (KMS). When you use KMS, you are charged for key management and API calls. For more information, see Billing of KMS.
   ESSD Performance Level	If you set the Deployment Mode parameter to Single-zone Deployment, this parameter is automatically set to PL1. If you set the Deployment Mode parameter to Multi-zone Deployment, this parameter is automatically set to Regional ESSD. You can subsequently change the ESSD performance level by scaling up your cluster based on your business requirements.
   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.

4. Perform the subsequent purchase operations as prompted based on the Product Type parameter that you selected.

   Approximately 10 to 15 minutes after you complete the payment, you can view the cluster on the Enterprise Edition or Basic Edition tab of the Clusters page.

   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.

Data Warehouse Edition in reserved mode

The single-node specifications of reserved resources for Enterprise Edition clusters are consistent with the specifications of Data Warehouse Edition clusters in reserved mode. The following table describes the specification mappings between Data Warehouse Edition in reserved mode and Enterprise Edition.

Data Warehouse Edition in elastic mode and Data Lakehouse Edition

If you have purchased Data Warehouse Edition clusters in elastic mode or Data Lakehouse Edition clusters, you can select specifications for Enterprise Edition clusters by using the following formula and parameters:

• M specifies the number of reserved computing resource cores in a Data Warehouse Edition or Data Lakehouse Edition cluster.

• N specifies the number of reserved storage resource cores in a Data Warehouse Edition or Data Lakehouse Edition cluster (24 cores × Number of sets of reserved storage resources).

• X specifies the number of reserved resource cores in an Enterprise Edition cluster (Single-node specifications of reserved resources × Number of reserved resource nodes).

An Enterprise Edition cluster that has a larger value of X provides better performance if the N < X <= M + N formula is met.

The following table describes the specification mappings between Data Warehouse Edition in elastic mode, Data Lakehouse Edition, and Enterprise Edition.