Parameter | Description |
Instance Mode | Select Serverless. |
Database Engine | Select MySQL. |
Region | Select a region for database deployment. Currently, the serverless billing mode is supported only in Guangzhou, Shanghai, Beijing, Nanjing, Hong Kong (China), Silicon Valley, Virginia, Singapore,Tokyo and Seoul regions. If you need to use it in other regions, submit a ticket for assistance. |
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 Yes is chosen, the option for a secondary availability zone will appear. |
Secondary Availability Zone | By default, this feature is disabled. Upon enabling multi-AZ deployment, you may select your standby availability zone. For regions and availability zones that support multi-AZ deployment, please refer to the Multi-AZ Deployment section. For the most up-to-date supported regions and availability zones, see the purchase page for accurate information. |
Transfer Linkage | It is "High IO" by default. |
Network | For performance and security considerations, only VPC network is supported currently. CVM instances can communicate with TDSQL-C instances only in the same VPC. |
Database Version | MySQL 5.7 and 8.0 are supported. |
Serverless Architecture | Supports the selection of either a Single-Node or Cluster architecture. Single-node architecture: The cluster contains only one read-write instance. After purchase, you can switch to a Cluster architecture by adding read-only instances through configuration adjustments in the console. Cluster architecture: The cluster comprises one read-write instance and 1 to 8 optional read-only instances. |
Compute Unit | Select the upper and lower limits of the TDSQL-C compute unit (CCU), and the instance will be automatically and elastically scaled within the selected resource range. CCU is the computing and billing unit for the serverless mode. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size. For more information, see Compute Unit. Single-node architecture: It is only necessary to configure the computational power range for the read-write instance. Cluster architecture: It is required to configure the computational power range for the read-write instance, select the number of read-only instances within the read-only group (1 - 8), and set the computational power range for the read-only instances. |
Auto-Pause | Configure the automatic pause time of the instance. If there is no connection to access the database within the set time, the instance will be automatically paused, with billing stopped. |
Parameter | Description |
Compute Billing Mode | Resource pack (monthly subscription) and pay-as-you-go billing are supported. The compute resource pack will be used preferably for the deduction of actual usage of pay-as-you-go products. When the pack is used up, the resource usage will be pay-as-you-go. Compute resource packs are deducted based on the actual CCU used per second. The resource pack mode is more cost-effective and flexible than the pay-as-you-go option. |
Compute resource pack (displayed when selecting Resource Pack in the compute billing mode) | Binding a resource pack allows you to associate one or more (up to a maximum of ten) compute resource packs with the cluster selected in the region under the current account, provided they are within their validity period. If there are no available resource packs, you may proceed to purchase a resource package first. |
Storage Billing Mode | Resource pack (monthly subscription) and pay-as-you-go billing are supported. The storage resource pack will be used preferably for the deduction of actual usage of pay-as-you-go products. When the pack is used up, the resource usage will be pay-as-you-go. Storage resource packs are deducted based on the actual storage used per hour. The resource pack mode is more cost-effective and flexible than the pay-as-you-go option. |
Storage resource pack (displayed when selecting Resource Pack in the storage billing mode) | Binding a resource pack allows you to associate one or more (up to a maximum of ten) storage resource packs with the cluster selected in the region under the current account, provided they are within their validity period. If there are no available resource packs, you may proceed to purchase a resource package first. |
Parameter | Description |
Cluster Name | Set a name for the cluster now or later. It must contain less than 60 letters, digits, or symbols (-_.). |
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. |
Custom Port | It is 3306 by default and can be customized. |
Parameter | Description |
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. |
Was this page helpful?