Creating Serverless Cluster

Last updated: 2025-10-23 20:28:00

Creating Serverless Cluster

Last updated: 2025-10-23 20:28:00

This document describes how to create a serverless cluster in the TDSQL-C for MySQL console.
Prerequisite
To make a purchase, you need to complete identity verification first. For more information, see Identity Verification Guide.
Directions
1. Log in to the purchase page to complete the Database Configuration, Instance Selection, and Storage settings, and then click Next.
Parameter
Description
Instance Mode
Select Serverless.
Serverless cost estimation is supported to help you better understand whether the cost of using the Serverless service meets your budget requirements. For more details, see Serverless Cost Estimator.
Instance Engine
Select a transactional cluster. The instance engine for Serverless clusters can only be set to transactional clusters.
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.
Currently, the serverless billing mode is supported only in Guangzhou, Shanghai, Beijing, Chengdu, 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‍
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 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
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.
Serverless Architecture
Supports the selection of either a Single-Node or Cluster architecture.
Single-node architecture: Within the cluster, there is only one read-write instance. Upon purchase, it supports switching to a clustered architecture via the console.
Cluster architecture: The cluster comprises one read-write instance and 1 to 15 optional read-only instances. Upon purchase, it supports switching to a single-node architecture via the console.
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 necessary to configure the computational power range for both read and write instances, followed by selecting the number of read-only instances within the read-only group (ranging from 1 to 15). Additionally, set the computational power range for nodes within the read-only group, which will be effective for all nodes in the group.
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.
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.
2. Complete the Basic Info settings and Advanced Configuration, select the purchase Quantity (each user can purchase up to 50 TDSQL-C for MySQL clusters in each AZ), and then click Buy Now after the fees are confirmed.
Basic Info
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.
Default collation rule
Select the default collation rule for the character set. Specific options are subject to the actual purchase page.
Custom Port
The default port is 3306, and custom input is supported. Port value range: 1024–65534.
Advanced Configuration
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.
3. After the purchase is completed, you will be redirected to the cluster list. After the status of the cluster becomes Running, it can be used normally.

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Parameter	Description
Instance Mode	Select Serverless. Serverless cost estimation is supported to help you better understand whether the cost of using the Serverless service meets your budget requirements. For more details, see Serverless Cost Estimator.
Instance Engine	Select a transactional cluster. The instance engine for Serverless clusters can only be set to transactional clusters. 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. Currently, the serverless billing mode is supported only in Guangzhou, Shanghai, Beijing, Chengdu, 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‍	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 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	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.
Serverless Architecture	Supports the selection of either a Single-Node or Cluster architecture. Single-node architecture: Within the cluster, there is only one read-write instance. Upon purchase, it supports switching to a clustered architecture via the console. Cluster architecture: The cluster comprises one read-write instance and 1 to 15 optional read-only instances. Upon purchase, it supports switching to a single-node architecture via the console.
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 necessary to configure the computational power range for both read and write instances, followed by selecting the number of read-only instances within the read-only group (ranging from 1 to 15). Additionally, set the computational power range for nodes within the read-only group, which will be effective for all nodes in the group.
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.
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.
Default collation rule	Select the default collation rule for the character set. Specific options are subject to the actual purchase page.
Custom Port	The default port is 3306, and custom input is supported. Port value range: 1024–65534.

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.

tencent cloud

Prerequisite

Directions