Parameter | Description |
Instance Mode | Select Provisioned Resource. |
Instance Engine | Select a transactional cluster. TDSQL-C for MySQL supports two instance engines: transactional cluster and analysis cluster. The transactional cluster can provide HTAP capability by enabling a read-only analysis engine in conjunction with TXSQL read-write instances, while the analysis cluster only contains read-only analysis engine instances and synchronizes the configured data source data to the analysis engine via Zero-ETL capability. |
Region | Select a region for database deployment. |
Source AZ | Select an AZ for deployment. Specific AZs in the selected region are shown on the actual purchase page. |
Multi-AZ Deployment | Select whether to enable multi-AZ deployment. If you enable it, the replica AZ option will appear. |
Replica AZ | It is disabled by default and can be selected after multi-AZ deployment is enabled. |
Transfer Linkage | It is "High IO" by default. |
Network | Select the network for a database instance. Currently, only Virtual Private Cloud (VPC) is supported. For performance and security reasons, only devices within the selected VPC can access this database instance through the private network. Use the private network for business access. For non-business access, such as testing or auxiliary management of a database, you can also access to the database instance through the public network. For detailed instructions and notes, see Enable or Disable Public Network Connection. |
Database Version | MySQL 5.7 and 8.0 are supported. |
Compute Billing Mode | Monthly subscription and pay-as-you-go billing are supported. |
Instance Type | Filtering computing specifications by instance type is supported. The supported options are as follows: all instance types, general, and exclusive. |
Compute Instance (read/write) | Select the compute specifications of the read-write instance. Only one read-write instance can be configured. Note: If your desired instance specification is sold out, you can click Do you need it? and the pop-up window will display instances of the same specification in other AZs. If none of them meet your requirements, submit a ticket for assistance. ![]() |
Compute Instance (read-only) | Select the computing specifications of the read-only instance. You can configure 0 to 15 read-only instances. The read-only instance type under a cluster supports the selection of preset resource instances (represented by the letter P) and Serverless resource instances (represented by the letter S). Among them, Serverless resource instances can automatically expand and contract according to load changes, and the actual calculation is in seconds. Charges will be charged based on usage and storage resource usage. After the instance is suspended, no computing fees will be charged. The total number of read-only instances in a cluster = number of preset resource instances + number of Serverless instances. You can add corresponding read-only instances as needed. ![]() Click Add Pre-Configured Resource Instances, select the required instance specification in the pop-up window, and click OK. If you need preset resource instances of the same instance specification, click "+" to increase the quantity. If you need preset resource instances of different instance specifications, you can click Add Pre-Configured Resource Instances again to select. If you need to modify the selected instance type, you can click Modify and reselect the required instance type. Click Add Serverless Resource Instances to complete the computing power configuration and automatic suspension settings. If you need to increase the number of instances after adding it, click "+" to increase it. Then uniformly set the computing power interval configuration for the selected Serverless resource instance. Selecting whether to enable automatic pause is supported. If the option is checked, the automatic pause time can be set, indicating that the database will automatically enter a paused status if it is not used within the set time period. During the paused status, no computing charges will be incurred; if the option is unchecked, the database will keep running continuously. The automatic pause settings can also be modified in the console after a cluster is created. (This step is required when adding a Serverless resource instance) Select the billing mode for the Serverless resource instance, which supports pay-as-you-go billing or resource pack. If you choose a resource pack, you can bind one or more (up to 10) computing resource pack in the selected region of the cluster within the validity period under the current account. If there is no resource pack available, you can purchase the resource pack first. After the resource pack quota is consumed, billing will continue according to the pay-as-you-go billing model. |
Auto-Renewal | Auto-renew the device monthly upon expiration if your account has sufficient balance Note: This item needs to be set only when the computing resource billing mode of the cluster is set to yearly/monthly subscription. |
Storage Billing Mode | Pay-as-you-go billing is supported, which means you don't need to specify a storage option when you make a purchase. TDSQL-C for MySQL is billed by the actual storage used per hour. Monthly subscription billing is supported, which means you need to purchase monthly-subscribed storage space now (billed in the entirety regardless of whether it is used up). Note: When the computing resource billing mode is set to yearly/monthly subscription, the storage resource billing mode can be set to either yearly/monthly subscription or pay-as-you-go. When the computing resource billing mode is set to pay-as-you-go, the storage resource billing mode can only be set to pay-as-you-go. For how to choose the billing mode for storage space, see How to Choose Storage Space Billing Mode. |
Parameter | Description |
Cluster Name | Set a name for the cluster now or later. It must contain up to 60 letters, digits, hyphens, underscores, and dots. |
Admin Username | It is root by default. |
Password | The password can contain 8–64 characters in at least three of the following character types: uppercase letters, lowercase letters, digits, and symbols ~!@#$%^&*_-+=|\\(){}[]:;',.?/. |
Default Character Set | UTF8, GBK, LATIN1, and UTF8MB4 are supported. |
Default collation rule | Select the default collation rule for the character set. Specific options are subject to the actual purchase page. |
Custom Port | It is 3306 by default and can be customized. |
Parameter | Description |
Enabling the database proxy | Select whether to enable the database proxy. The options are yes and no. Select yes: Set the proxy specification, AZ, and number of nodes. For setting item description, see Enabling the Database Proxy. Select no: This option indicates that the database proxy is not enabled when a cluster is created. After creation, you can enable the database proxy through the console. |
Security Group | Select or create a security group. |
Parameter Template | Select or create a parameter template. |
Table Name Case Sensitivity | Select Case-Insensitive or Case-Sensitive. |
Project | Specify a project for the cluster to be created. |
Alarm Policy | Select or create an alarm policy. |
Tag | Add a tag to facilitate resource categorization and management. |
Terms and Conditions | Read and indicate your consent to the terms and conditions. |

Feedback