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 the deployment region for your database. For the regions where Serverless is currently supported for deployment, see Multi-AZ Deployment Overview. If the region you need to deploy to is not listed, you can submit a ticket to provide feedback. |
Source AZ | Select the AZ for deployment. The AZ distribution in the corresponding region is subject to the actual purchase page. |
Multi-AZ Deployment | Select whether to enable multi-AZ deployment. If you select Yes, the secondary AZ option will appear. |
Replica AZ | Disabled by default. After you enable multi-AZ deployment, you can select your secondary AZ. For the regions and AZs that support multi-AZ deployment, see Multi-AZ Deployment. For the latest supported regions and AZs, refer to the purchase page. |
Transfer Linkage | High IO Edition by default. |
Network | Select the network for the database instance. Currently, only Virtual Private Cloud (VPC) is supported. For security and performance considerations, only devices within the selected VPC can access this database instance through the private network. For business access, use the private network. For non-business access, such as testing or auxiliary database management, you can also access the database instance via the public network. For detailed instructions and considerations, see Enable or Disable Public Network Connection. |
Database Version | MySQL 5.7 and 8.0 are supported. |
Custom Kernel Minor Version | Select the kernel minor version. The supported options are Default and Custom. Default: Selecting this option indicates that the system automatically assigns the kernel minor version. Custom: When you select Custom, you can choose a specific version under the Stable or New Feature edition. Stable Edition: A stable version that has undergone long-term validation, with an update frequency of 3 to 4 months. New Feature Edition: It carries new features and is a general kernel minor version for the production network. |
Compute Billing Mode | You can select pay-as-you-go or a resource pack. A compute resource pack with a fixed quota is used to preferentially offset the actual usage generated by pay-as-you-go products. After the resource pack quota is exhausted, billing continues according to the pay-as-you-go billing mode. The compute resource pack is deducted based on the actual CCU usage per second, which is more cost-effective and flexible compared to the pay-as-you-go mode. |
Compute Resource Pack (displayed when selecting Resource Pack in the compute billing mode) | Bind resource packs. You can bind one or more (up to 10) compute resource packs that are under your current account, within their validity period, and in the region selected for the cluster. If no resource packs are available, you can purchase a resource pack first. |
Serverless | Both single-node edition and cluster edition architectures are supported. Single-node edition architecture: A cluster with one read-write instance. It can be switched to cluster edition architecture in the console after purchase. Cluster edition architecture: A cluster with one read-write instance and 1-15 read-only instances (optional). It can be switched to single-node edition architecture in the console after purchase. |
Compute Unit | Select the upper and lower limits for the compute configuration CCU (TDSQL-C Compute Unit). The instance automatically performs elastic scaling based on the selected resource range. CCU (TDSQL-C Compute Unit) is the compute billing unit for Serverless. One CCU is approximately equal to the compute resources of 1 CPU and 2 GB of memory. The number of CCUs used in each billing cycle is: the greater of the number of CPU cores used by the database and half of the memory size. For compute configuration, see Service Compute Configuration. Single-node architecture: You only need to set the computing power range for the read-write instance. Cluster edition architecture: You need to set the computing power range for the read-write instance, then select the number of read-only instances (1-15) in the read-only group and set the computing power range for the nodes within the read-only group. This computing power range applies to all nodes in the read-only group. |
Auto-Pause | Configure the instance auto-pause time. If no connections access the database within the set time, the instance will be paused automatically. After the instance is paused, compute resources will no longer be billed. |
Storage Billing Mode | You can select pay-as-you-go or a resource pack. A storage resource pack with a fixed quota is used to preferentially offset the actual usage generated by pay-as-you-go products. After the resource pack quota is exhausted, billing continues according to the pay-as-you-go billing mode. The storage resource pack is deducted based on the actual storage usage per hour, which is more cost-effective and flexible compared to the pay-as-you-go mode. |
Storage Resource Pack (displayed when selecting Resource Pack in the storage billing mode) | Bind resource packs. You can bind one or more (up to 10) storage resource packs that are under your current account, within their validity period, and in the region selected for the cluster. If no resource packs are available, you can purchase a resource pack first. |
Parameter | Description |
Cluster Name | You can choose to name the instance after creation or immediately. Only Chinese characters, letters, digits, underscores (_), hyphens (-), and periods (.) are supported. The length should be less than 60 characters. |
Administrator Username | The default name is root. |
Password | 8–64 characters, including any three of the following types: uppercase and lowercase letters, digits, and ~!@#$%^&*_-+=|\\(){}[]:;'<>,.?/. |
Default Character Set | UTF-8, 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 |
Enable Database Proxy | Select whether to enable the database proxy. The options are yes and no. Select yes: Configure the proxy specification, AZ, and number of nodes. For descriptions of these settings, see Enabling the Database Proxy. This option is available only when the automatic pause option is not selected. 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. |
Enable AI Optimizer | The AI optimizer is used to improve SQL efficiency. Select whether to enable the AI optimizer (cluster dimension). Default value: yes. Value range: yes, no. For detailed feature introduction, see AI Optimizer Overview. |
Security Group | Manually select a security group. The security group is optional. After the instance is created, you can manually add or modify the security group on the read-write instance. |
Parameter Template | Select or create a parameter template. |
Table Name Case Sensitivity | Select whether table names are case-sensitive. The options are case-insensitive and case-sensitive. |
Project | Specify an associated project for the cluster you want to create. |
Alarm Policy | Select or create an alarm policy. |
Tag | Add tags to facilitate resource classification and management. |
Terms and Conditions | Read and check the agreement terms. |
API | Description |
This interface (DescribeZones) is used to query information about available regions and AZs for purchase. | |
This API (DescribeServerlessInstanceSpecs) is used to query the optional specifications for Serverless instances. | |
This API (InquirePriceCreate) is used to query the price for purchasing a new cluster. | |
This API (InquirePriceMultiSpec) is used for batch price inquiry. | |
This API (CreateClusters) is used to purchase new clusters. | |
This API (DescribeResourcesByDealName) is used to query instances associated with an order. |
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários