Create a cluster

1. Sign in to the AnalyticDB for MySQL console. In the upper-right corner, click Buy Cluster.

2. Select a Product Type.

   • Pay-as-you-go: An hourly, post-paid billing method suitable for short-term needs. You can release the cluster at any time to save costs.

   • Subscription: A pre-paid billing method ideal for long-term needs. It is more cost-effective than pay-as-you-go, offering greater discounts for longer terms.

3. Configure the parameters and click Buy Now in the lower-right corner.

   Parameter	Description
   Edition	Select Enterprise Edition or Basic Edition. Enterprise Edition uses a multi-replica architecture for storage, providing distributed capabilities and high availability. Basic Edition uses a single-replica architecture for storage and does not provide high availability. For more information about Enterprise Edition and Basic Edition, see Product editions.
   Deployment Mode	Enterprise Edition: Supports Single-zone Deployment or Multi-zone Deployment. Important Multi-zone deployment is supported only in the China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), China (Hong Kong), and Singapore regions. Basic Edition: Supports only Single-zone Deployment.
   Region	The geographic location of the cluster. This setting cannot be changed after purchase. For the lowest latency, select the region closest to your workloads.
   Primary Zone	Select a primary availability zone for the cluster.
   Secondary Zone	Select a secondary availability zone for the cluster. If the primary availability zone fails, services automatically fail over to the secondary zone. This process may cause temporary read or write failures and timeouts. Important Configure this parameter only when Deployment Mode is set to Multi-zone Deployment.
   Service-Linked Role	This role allows AnalyticDB for MySQL to create cluster-related resources by using the AliyunServiceRoleForAnalyticDBForMySQL service-linked role.
   Virtual Private Cloud (VPC) vSwitch in Primary Zone vSwitch in Secondary Zone	If you have already created a VPC that meets your network requirements, select that VPC. For example, if you have an ECS instance in a suitable VPC, select that VPC. If you do not have a suitable VPC, you can use the default VPC and vSwitch. For more information, see Default VPCs and vSwitches. If the default VPC and vSwitch do not meet your requirements, you can create your own. For instructions, see Create and manage a VPC. Important If you use other Alibaba Cloud services such as ECS or RDS, ensure your AnalyticDB for MySQL cluster is in the same VPC as the other services. Otherwise, they cannot communicate over the internal network, which can degrade performance. Configure the vSwitch in Secondary Zone parameter only when Deployment Mode is set to Multi-zone Deployment.
   Automatically activate PVL service	After activating the PVL (PrivateLink) service, you can securely access AnalyticDB for MySQL over a private network. This ensures secure and efficient network communication and avoids the security risks of public network access. You must activate the PVL service to create a cluster. Each Alibaba Cloud account needs to activate the service only once. Activation is free of charge. Note If the purchase page does not prompt you to activate the PVL service, it is already activated and you do not need to select this option.
   Single-node Specifications of Reserved Resources	The default specification for a single node is 8 ACUs. Reserved resources can be used for the following purposes: Data computing: Adding more reserved resources can improve query speed. Hot data storage: One group of reserved resources supports up to 8 TB of hot data storage. You are billed for hot data storage based on your actual usage. Note If you have previously purchased Data Warehouse Edition or Data Lakehouse Edition clusters, see Specification mapping between Enterprise, Data Lakehouse, and Data Warehouse editions to select the corresponding Enterprise Edition specifications.
   Reserved Resource Nodes	For an Enterprise Edition cluster, the default is 3, in increments of 3. Note In Enterprise Edition , you can set the number of reserved resource nodes to 0. In this case, the purchase price for the reserved resource nodes is not displayed. Note the following: If the number of reserved resource nodes is 0, you can use only external tables. To create AnalyticDB for MySQL internal tables, the number of reserved resource nodes must be at least one. If you set the number of reserved resource nodes to 0 when you create the cluster, you can purchase reserved resources later by scaling out the cluster. For details, see Scale out or scale in Enterprise and Basic edition clusters. For a Basic Edition cluster, the default is 1, in increments of 1.
   Disk Encryption	If you enable disk encryption, the system encrypts the entire data disk at the block storage level. This protects your data by ensuring that backups remain encrypted and unreadable even if compromised. If this is the first time you are using this feature, after enabling Disk Encryption, you must also Create Service-linked Role and select a target key from the Key drop-down list. For detailed steps, see Disk encryption. Important You can enable disk encryption only during cluster creation.AnalyticDB for MySQL This feature cannot be changed afterward. The disk encryption feature uses Key Management Service (KMS). When you use this feature, you are charged for key management and API calls. For more information about KMS service fees, see KMS 1.0 Billing.
   ESSD Performance Level	If Deployment Mode is set to Single-zone Deployment, the ESSD performance level for a new cluster is fixed at PL1. If Deployment Mode is set to Multi-zone Deployment, the ESSD performance level for a new cluster is fixed at Regional ESSD. If needed, you can change the ESSD performance level later by scaling up the cluster.
   Version update policy	The cluster automatically updates to the latest version within the maintenance window. The default maintenance window is from 12:00 to 13:00. You can change the maintenance window after you purchase the cluster. For more information, see Configure a maintenance window.

4. Based on your selected Product Type, follow the prompts on the console to complete the purchase.

   After your payment is successful, wait about 10 to 15 minutes. You can then view the new cluster on the Enterprise Edition or Basic Edition tab of the Clusters page.

   Note

   • After you create a cluster, you can purchase an ACU-hour plan. This plan allows you to buy a fixed amount of ACU-hours at a lower unit price to offset the fees of your pay-as-you-go ACU resources. No additional fees are charged for the offset resources. For more information about ACU-hour plans, see ACU-hour plan.

   • You can also purchase a storage plan to obtain a fixed amount of storage capacity at a cheaper unit price, which can be used to offset the costs of pay-as-you-go hot and cold storage. For more information about storage plans, see Storage Plan.

Data Warehouse Edition Reserved Mode

The single-node specifications of reserved resources for Enterprise Edition are identical to the specifications of Data Warehouse Edition in reserved mode. This allows for a direct mapping.

Data Warehouse Edition Elastic Mode and Data Lakehouse Edition

If you previously purchased a Data Warehouse Edition cluster in elastic mode or a Data Lakehouse Edition cluster, use the following formula when purchasing Enterprise Edition:

• M = Reserved computing resource cores of your Data Warehouse Edition or Data Lakehouse Edition cluster.

• N = Reserved storage resource cores of your Data Warehouse Edition or Data Lakehouse Edition cluster (24 cores/192 GB × number of groups).

• X = Reserved resource cores of the Enterprise Edition cluster (single-node specifications × number of reserved resource nodes).

If N < X <= M+N, a larger value of X provides better performance.

The following table lists the mappings for the most commonly purchased specifications.