AnalyticDB：Create a cluster

Create a Data Lakehouse Edition 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 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.

7. 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 Data Lakehouse 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.

Create a Data Warehouse Edition 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 Edition, Region, Zone, VPC, and vSwitch parameters.

   Parameter	Description
   Edition	The edition of the cluster. Select Data Warehouse 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.
   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.
   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.
   Disk Encryption	If you select Disk Encryption, the system encrypts data on each data disk of your cluster based on Elastic Block Storage (EBS). 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. You cannot disable the disk encryption feature after the feature is enabled. 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.
   SSL Encryption	If you select SSL Encryption, the SSL encryption feature is automatically enabled for the created cluster. By default, VPC endpoints are encrypted. The SSL encryption feature can encrypt connections at the transport layer to improve data security, ensure data integrity, and prevent data listening, interception, and tampering.

4. Set the Mode parameter to Elastic Mode or Reserved Mode, configure the corresponding parameters, and then click Buy Now in the lower-right corner of the page.

   Note

   For more information about the elastic mode and reserved mode, see Editions.

   Elastic Mode

   The following table describes the parameters that must be configured if you set the Mode parameter to Elastic Mode.

   Parameter	Description
   Edition	For Elastic Mode, the Edition parameter is automatically set to Elastic Cluster. Elastic Mode for Cluster Edition uses a storage-compute decoupled architecture to provide capabilities such as elastic scaling, multi-tenant isolation, tiered storage of hot and cold data, heterogeneous storage, and user programming. This implements flexible real-time analysis with high performance at low resource costs.
   Specifications	The Specifications of the cluster. The parameter is automatically set to E32.
   Computing Resources	The computing resources of the cluster. You can use computing resources to compute data. The increase in the computing resources can accelerate data queries. The computing resources are available in Cluster Edition and Standalone Edition. Computing resources in Cluster Edition include 16 cores and 64 GB memory, 24 cores and 96 GB memory, and 32 cores or more. Cluster Edition supports resource isolation, scheduled scaling, and tiered storage of hot and cold data. Computing resources in Standalone Edition include 8 cores and 32 GB memory and 16 cores and 64 GB memory. Alibaba Cloud does not provide a service-level agreement (SLA) guarantee for Standalone Edition, and 4 to 8 hours are required for a failover. We recommend that you do not use Standalone Edition in production environments.
   ESSD Performance Level	The ESSD performance level of the cluster. This parameter is automatically set to PL1. You can change the ESSD performance level by scaling up the cluster based on your business requirements. For more information, see Scale a Data Warehouse Edition cluster.
   EIU Specifications	The single-node specifications of an elastic I/O unit (EIU) for clusters in elastic mode. This parameter is automatically set to 8 cores and 64 GB memory. Each EIU consists of three nodes and has 24 cores and 192 GB memory (8 cores × 3 and 64 GB × 3). Elastic I/O resources are bundled into units and sold as EIUs. You can use EIUs to scale up storage resources for clusters. For more information, see Elasticity of the storage layer.
   EIUs	The number of EIUs that are required to store data. You can configure this parameter based on the storage performance metrics of EIUs. For more information, see the "EIU-based storage performance metrics" table of the Elasticity of the storage layer topic. Alternatively, you can purchase one EIU when you create a cluster, and then purchase more EIUs by scaling up the cluster. For more information, see Scale a Data Warehouse Edition cluster. Note The EIUs parameter takes effect only when the Computing Resources parameter is set to 32 Cores and 128 GB or higher specifications.

   Reserved Mode

   The following table describes the parameters that must be configured if you set the Mode parameter to Reserved Mode.

   Parameter	Description
   Edition	For Reserved Mode, the Edition parameter is automatically set to Reserved Cluster. Reserved Mode for Cluster Edition uses a high-availability architecture that consists of three replicas to provide data reliability that is required in the finance industry. The nodes and storage capacity can be scaled within seconds to allow you to read and write data in real time with higher throughput.
   Specifications	The specifications of the cluster.
   Node Groups	The number of node groups. By default, each node group consists of three nodes.
   Storage Capacity	The storage of a single node group. If you purchase multiple node groups, you can calculate the total storage of the cluster by using the following formula: Total storage = Storage per node group × Number of node groups.

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

   After you complete the payment, you can view that the cluster is in the Preparing state on the Data Warehouse Edition tab of the Clusters page. As the progress bar reaches 100% after approximately 10 to 15 minutes, the status of the cluster changes to Running and you can use the cluster as expected.