Configuration Item | Description |
Instance Form | Select Serverless, which is billed based on the actual computing power (CCU) and storage space used, without the need to reserve resources with fixed specifications. It is suitable for scenarios with significant business load fluctuations, intermittent usage, or unpredictable capacity requirements. |
Billing Mode | Serverless instances only support the Pay as You Go billing mode, which charges based on the actual computing power (CCU) and storage space used. |
Region | Select the region where your business needs to be deployed. It is recommended to select the same region as your CVM. Cloud products in different regions cannot communicate via the private network, and the region cannot be changed after purchase. |
Database Mode | Compatible with MySQL 8.0: It is compatible with the MySQL 8.0 protocol. Compatible with HBase: It is compatible with HBase data types and APIs. |
Kernel Version | Select the required kernel version. |
Deployment Mode | Currently, only Single-AZ deployment is supported, meaning all resources are located in the same AZ, resulting in the lowest network latency. Single-AZ deployment carries disaster recovery risks. It is recommended to choose multi-AZ deployment for production environments. |
AZ | Select the AZ for instance deployment. Cloud products in different AZs under the same VPC can communicate via the private network. For example, a CVM in Guangzhou Zone 2 can access TDSQL Boundless in Guangzhou Zone 3 via the private network within the same VPC. |
Configuration Item | Description |
Compute Configuration | CCU (Cloud Computing Unit) is the computing power metering unit for TDSQL Boundless. The specification of one CCU is one CPU core and 2 GB of memory. Set the minimum and maximum computing power (CCU) for a single node. The Serverless instance automatically scales between the minimum computing power and maximum computing power based on the business load. The default value range is 1 CCU - 16 CCU. |
Number of Nodes | Defaults to 2, meeting the requirements for high-availability deployment. |
Storage Billing Mode | The storage space of Serverless instances uses the Pay as You Go billing mode, which is settled based on the actual storage capacity occupied, and does not require pre-specifying a storage specification. |
Configuration Item | Description |
Network | Supports VPC environments, allowing you to select the network and subnet for the instance. If the existing network is unsuitable, you can create a VPC or create a subnet. Note: A subnet is a network space that is logical within a VPC. You can create subnets in different AZs under the same VPC. Subnets in different AZs under the same VPC can interconnect via the private network by default. After you select a network, the subnet is displayed by default as the subnet IP address in the same AZ as the selected instance. You can also manually select a subnet IP address from other AZs within the same region. Actual business connections follow the nearest principle, which does not increase network latency. It is recommended that you select a VPC in the same region as your CVM. Otherwise, you cannot connect to the CVM and the database via the private network. The default setting is Default-VPC (default). |
Custom Port | The database access port, which defaults to 3306, has a valid range: 1024 - 65535. |
Tag | Add Tags to instances for categorized management of instance resources. |
Configuration Item | Description |
Instance Name | Name It Later: Set the instance name after the instance is created. Name It Now: Set the instance name directly during creation. |
Parameter templates | Select the required parameter template from the drop-down list. This applies only to instances with kernel version ≥ 21.6.x. Read/Write Balanced (Default): Suitable for general business scenarios. Write Optimized: Suitable for write-intensive workloads. Read Optimized: Suitable for read-intensive workloads. |
Character Set | Applies only to MySQL compatibility mode. The default value is UTF8MB4. Common optional values include UTF8, LATIN1, GBK, UTF8MB4, GB18030, and others. |
Table Name Case Sensitivity | Applies only to MySQL compatibility mode. Specifies whether table names are case-sensitive. In MySQL compatibility mode, the case sensitivity setting for table names cannot be changed after configuration. Please configure with caution. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback