Create a cluster

1. Log on to the AnalyticDB for MySQL console. Click Purchase Instance in the upper-right corner.

2. Select Product Type.

   • Pay-as-you-go: This postpaid billing method is billed hourly and is suitable for short-term use. You can release the cluster immediately after use to save costs.

   • Subscription: This prepaid billing method requires payment upon cluster creation and is suitable for long-term use. Subscription is more cost-effective than pay-as-you-go, offering lower prices for longer durations.

3. After setting the parameters, click Buy Now in the lower-right corner.

   Parameter	Description

   Parameter	Description
   Edition	Select Enterprise Edition or Basic Edition. Enterprise Edition uses a multi-replica architecture. The underlying storage is multi-replica and provides distributed capabilities and high availability. Basic Edition uses a single-replica architecture. The underlying storage is single-replica and does not provide high availability. For more information about Enterprise Edition and Basic Edition, see Product series.
   Deployment Mode	Enterprise Edition: Supports Single-zone Deployment or Multi-zone Deployment. Important Only the China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), Hong Kong (China), and Singapore regions support multi-zone deployment. Basic Edition: Fixed as Single-zone Deployment.
   Region	The region where 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	Select the primary zone where the cluster resides.
   Secondary Zone	Select the secondary zone where the cluster resides. When the primary zone fails, the service automatically switches to the secondary zone. During the switch, the cluster may become unreadable or unwritable, or experience read or write timeouts. Important Specify this parameter only when the Deployment Mode is set to Multi-zone Deployment.
   Service-linked Role	Allow the AnalyticDB for MySQL service to create cluster-related resources through the AliyunServiceRoleForAnalyticDBForMySQL role.
   Virtual Private Cloud (VPC) Primary Zone Vswitch Secondary Zone Vswitch	If you have created a VPC that meets your business requirements, select the VPC. For example, if you have created an ECS instance and the VPC to which the ECS instance belongs meets your network requirements, select this 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 VPC and vSwitch. If the default VPC and vSwitch cannot meet your business requirements, you can create a VPC and a vSwitch. For more information about how to create a VPC and a vSwitch, see Create and manage a VPC. Important If you are using other Alibaba Cloud services such as Elastic Compute Service (ECS) or ApsaraDB RDS, make sure that AnalyticDB for MySQL and other cloud services are in the same VPC. Otherwise, they cannot communicate with each other over the internal network and cannot achieve optimal performance. Specify the Deployment Mode as Multi-zone Deployment to specify the Secondary Zone Vswitch.
   Automatically Activate Privatelink	After you activate the PrivateLink service, you can securely access AnalyticDB for MySQL over a private network. This ensures secure and efficient network communication and avoids potential security risks associated with accessing services over the Internet. 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 on the purchase page, PrivateLink is already 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. 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 previously purchased the Data Warehouse Edition or Data Lakehouse Edition, see Mapping between Enterprise Edition and Data Lakehouse Edition or Data Warehouse Edition specifications for the specifications of Enterprise Edition. If the amount of reserved resources is 0 ACUs, you can use only external tables. If you want to create internal tables in AnalyticDB for MySQL, the amount of reserved resources must be greater than 0 ACUs. If you select 0 ACUs as the reserved resources when you create a cluster, you can purchase reserved resources by performing a scale-out after the cluster is created. For more information, see Scale-out and scale-in for Enterprise Edition and Basic Edition.
   Number Of Reserved Resource Nodes	The default number of reserved resource nodes for an Enterprise Edition cluster is 3. The step size is 3. The default number of reserved resource nodes for a Basic Edition cluster is 1. The step size is 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 it is leaked. If you use this feature for the first time, after you select Disk Encryption, you also need to Create A Service-linked Role and select the target Key from the drop-down list. For more information about the detailed procedure, see Disk encryption. Important Disk encryption can be enabled only when you create an AnalyticDB for MySQL cluster. After the cluster is created, you cannot enable or disable this feature. 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 about the fees of KMS, see KMS billing.
   Disk Category	When the Deployment Mode is set to Single-zone Deployment, the disk category of a newly purchased cluster is fixed as PL1. When the Deployment Mode is set to Multi-zone Deployment, the disk category of a newly purchased cluster is fixed as ESSD Zone-redundant Storage.
   Version Upgrade Policy	The policy that is used to upgrade the cluster version. The cluster is automatically upgraded to the latest version within a specified 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 Set the maintenance window.

4. Based on the selected Product Type, complete the purchase operations as prompted by the console.

   After successful payment, wait approximately 10 to 15 minutes to see the newly created cluster on the Cluster list page under the Enterprise Edition or Basic Edition tab.

   Note

   • After creating a cluster, you can purchase ACU-hour plans with a specific number of ACU-hours at reduced costs to offset pay-as-you-go ACU resource usage. For more information about ACU-hour plans, see ACU-hour plans.

   • You can also purchase storage plans with a specific amount of resources at reduced costs to offset pay-as-you-go hot and cold data storage. For more information about storage plans, see Storage plans.

Data warehouse edition reserved mode

The single-node specifications of reserved resources for Enterprise Edition are the same as those for the Data Warehouse Edition reserved mode. A simple mapping is all that's required.

Data warehouse edition elastic mode and Data Lakehouse Edition

If you have previously purchased a Data Warehouse Edition cluster in elastic mode or a Data Lakehouse Edition cluster, use the following formula to select the specifications of Enterprise Edition:

• M = The number of reserved computing resources for Data Warehouse Edition or Data Lakehouse Edition.

• N = The number of reserved storage resources for Data Warehouse Edition or Data Lakehouse Edition (24 cores and 192 GB memory × number of groups).

• X = The number of reserved resources for Enterprise Edition (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 table below describes the specification mappings between Data Warehouse Edition in elastic mode, Data Lakehouse Edition, and Enterprise Edition.