Buying a Pay-per-Use DB Instance

Scenarios

This section describes how to create a pay-per-use DB instance on the TaurusDB console.

Billing

After you buy a pay-per-use DB instance, you will be billed for resources you actually use. For billing details, see Pay-per-Use Billing.

Procedure

1. Go to the Buy DB Instance page.
2. On the displayed Custom Config page, configure required information and click Next.
   • Basic configuration
     Figure 1 Basic configuration
     

     Table 1 Basic configuration

     Parameter	Description
     Billing Mode	Select Pay-per-use.
     Region	Region where an instance is deployed. NOTE: You cannot change the region of an instance once it is purchased.

   • Resource selection
     Figure 2 Resource selection
     

     Table 2 Resource selection

     Parameter	Description
     DB Engine Version	Only TaurusDB V2.0 is supported.
     Kernel Version	DB kernel version. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History. NOTE: To specify the kernel version when buying an instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
     Creation Method	How an instance is created. The value can be Create new or Migrate from RDS. Create new: A new TaurusDB instance will be created. Migrate from RDS: If you want to migrate data from an RDS instance to a TaurusDB Enterprise Edition instance, select Migrate from RDS. To use this function, submit a request in the upper right corner of the management console.
     DB Instance Type	Select Cluster, Single, or Multi-primary. Cluster: A cluster instance can contain one primary node and 1 to 15 read replicas. The primary node processes read and write requests, and the read replicas process only read requests. If the primary node becomes unavailable, TaurusDB automatically fails over to a read replica. Cluster instances apply to medium- and large-sized enterprises in the Internet, taxation, banking, and insurance sectors. Single: A single-node instance contains only one primary node and there are no read replicas. Single-node instances do not involve data synchronization between nodes and can easily ensure atomicity, consistency, isolation, and durability of transactions. They are only recommended for development and testing of microsites, and small and medium enterprises, or for learning about TaurusDB. Multi-primary: A multi-primary instance can contain 2 to 63 primary nodes, with no read replicas. Such an instance can process multiple reads and writes, delivering excellent read/write performance at high concurrency. For more information about multi-primary instances, see Multi-primary Instances (OBT). The kernel version of a multi-primary instance must be: 2.0.63.250300, 2.0.60.241201, 2.0.60.241200, 2.0.57.240922, 2.0.57.240920, 2.0.57.240905, or 2.0.57.240900 NOTE: To buy a multi-primary instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
     AZ Type	An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Some regions support both single-AZ and multi-AZ deployment and some only support single-AZ deployment. Single-AZ: The primary node and read replicas are deployed in the same AZ. Multi-AZ: The primary node and read replicas are deployed in different AZs to achieve higher availability and reliability. It is suitable for workloads that require cross-AZ DR or are insensitive to cross-AZ latency.
     Storage Type	DL6 The original shared storage. The default storage type of TaurusDB instances created before July 2024 is shared storage, while that of TaurusDB instances created in July 2024 and beyond is DL6. DL6-based instances achieve zero RPO with a 3-AZ deployment and deliver better performance and higher peak throughput. They are suitable for core application systems that are sensitive to performance and have demanding requirements on storage I/O during peak hours, such as those in finance, e-commerce, government, and gaming. DL5 A new type of storage. With Huawei Cloud's hardware and network infrastructure technologies, DL5-based instances maintain the same high availability (zero RPO in the 3-AZ deployment) as DL6-based instances. Although the peak performance of DL5-based instances may be a bit less than what you get with DL6-based instances, the cost per unit of capacity is a lot less. DL5-based instances are suitable for CPU-intensive sub-core business systems, or application modules that need to minimize costs. For more information about storage types, see Storage Types.

   • Instance options
     Figure 3 Specifications and storage
     

     Table 3 Specifications and storage

     Parameter	Description
     Resource Type	Select Shared.
     Instance Specifications	TaurusDB is a cloud-native database that uses the shared storage. To ensure that instances run stably under high read/write pressure, TaurusDB controls the read/write peaks of instances based on instance specifications. For details about how to select instance specifications, see Performance White Paper. For more information about instance specifications, see Instance Specifications. After a DB instance is created, you can change its vCPUs and memory.
     CPU Architecture	Select x86 or Kunpeng. x86: x86 instances use Intel® Xeon® Scalable processors and feature robust and stable computing performance. When working on high-performance networks, the instances provide the additional performance and stability that enterprise-class applications demand. Kunpeng: Kunpeng instances use Kunpeng 920 processors and 25GE high-speed intelligent NICs for powerful compute and high-performance networks, making them an excellent choice for enterprises needing cost-effective, secure, and reliable cloud services.
     Nodes	This parameter is mandatory for cluster instances. By default, each instance can contain one primary node and multiple read replicas. You can create up to 9 read replicas for a pay-per-use instance at a time. After an instance is created, you can add read replicas as required. Up to 15 read replicas can be added to an instance. For details, see Adding Read Replicas to a DB Instance.
     Storage	It contains the system overhead required for inodes, reserved blocks, and database operations. Storage of a pay-per-use instance will be scaled up dynamically based on the amount of data that needs to be stored, and is billed hourly on a pay-per-use basis.
     Backup Space	TaurusDB provides free backup space equal to the amount of your used storage. After the free backup space is used up, you will be billed for the additional space on a pay-per-use basis.
     TDE	Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively protects the security of databases and data files. After TDE is enabled, you need to select the cryptographic algorithm AES256 or SM4 as needed. NOTE: To use TDE, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. For details about TDE constraints, see Enabling TDE for a DB Instance.

     Figure 4 Network
     

     Table 4 Network

     Parameter	Description
     VPC	A dedicated virtual network where your instance is located. It isolates networks for different workloads to enhance security. TaurusDB allocates a default VPC (default_vpc) for your instance. You can also use an existing, new, or shared VPC. After the TaurusDB instance is created, the VPC cannot be changed. To use an existing VPC, select an existing VPC under the current account from the drop-down list. To use a new VPC, create a VPC first and then select the VPC from the drop-down list. For details about how to create a VPC, see Creating a VPC and Subnet in Virtual Private Cloud User Guide. To use a shared VPC, select a VPC that another account shares with the current account from the drop-down list. With Resource Access Manager (RAM), you can share subnets in a VPC with one or more accounts, so you can easily configure and manage multiple accounts' resources at low costs. For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide.
     Subnet	A subnet provides dedicated network resources that are logically isolated from other networks for network security. Subnets take effect only within an AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets where DB instances are located and cannot be disabled. TaurusDB supports both IPv4 and IPv6 networks. Instances using IPv4 and IPv6 cannot be in the same subnet. IPv4 A private IPv4 address is automatically assigned when you create a DB instance. You can also enter an idle private IPv4 address within the subnet CIDR block. After the DB instance is created, the private IPv4 address can be changed. IPv6 IPv6 addresses are used to deal with IPv4 address exhaustion. To enable IPv6, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. After IPv6 is enabled, if you want to create an instance using IPv4, you need to select an IPv4 subnet. You can create a DB instance that uses a private IPv6 address only when its specifications support IPv6. Instance specifications supporting IPv6 vary depending on regions and AZs. Whether instance specifications support IPv6 is displayed on the console after a region and an AZ are selected. IPv6 needs to be enabled for subnets where TaurusDB instances are located. If IPv6 is not enabled, enable it by following the instructions provided in Creating a VPC and Subnet. Figure 5 Enabling IPv6 for a subnet
     Security Group	A security group enhances security by controlling access to TaurusDB from other services. When you select a security group, you must ensure that it allows the client to access DB instances. If no security group is available or has been created, TaurusDB allocates a security group to your DB instance by default. To ensure subsequent database connection and access, you need to allow all IP addresses to access your DB instance through port 3306 and over ICMP. If the port and protocol are not enabled for the selected security group, click Add Inbound Rule as prompted and complete the configuration in the displayed dialog box. For details, see Configuring Security Group Rules.

     Figure 6 Setting an administrator password
     

     Table 5 Database configuration

     Parameter	Description
     DB Instance Name	The name must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed. If you create multiple instances at a time, a hyphen (-) followed by a number with four digits will be appended to the instance name, starting with -0001. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on. The names for instances created in batches must consist of 4 to 59 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. NOTE: To use Chinese characters, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
     Administrator Password	The default administrator account is root. The administrator password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?,()&$|.). Enter a strong password and periodically change it to improve security and defend against threats such as brute force cracking attempts. If you select a custom parameter template during instance creation, the administrator password must comply with the values of validate_password parameters in the custom parameter template. Otherwise, the instance creation will fail. To check the parameter values, go to the Parameter Templates page, find the target parameter template and click its name. In the upper right corner of the page, search for validate_password. Keep this password secure. If lost, the system cannot retrieve it. After a DB instance is created, you can reset this password. For details, see Resetting the Administrator Password.
     Confirm Password	Enter the administrator password again.

   • Advanced settings and required quantity
     Figure 7 Advanced settings and required quantity
     

     Table 6 Advanced settings

     Parameter	Description
     Database Proxy	Enabled by default. After a proxy instance is created, you can use the proxy address to connect to your DB instance. NOTE: To create a proxy instance when buying a DB instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. You can also create proxy instances after buying a DB instance. For details, see Creating a Proxy Instance for Read/Write Splitting.
     Proxy Mode	You can select Read/Write or Read-only as needed. Read/Write: All write requests are forwarded only to the primary node, and all read requests are forwarded to the selected nodes based on the read weights. Read-only: Write requests are not forwarded to any node. The primary node does not process write and read requests, and all read requests are forwarded to the selected read replicas based on read weights.
     Proxy Instance Specifications	You can select the proxy instance specifications as needed.
     Enterprise Project	Only available for enterprise users. If you want to use this function, contact customer service. An enterprise project provides a way to manage cloud resources and enterprise members on a project-by-project basis. You can select an enterprise project from the drop-down list. The default project is default.
     Parameter Template	Contains engine configuration values that can be applied to one or more instances. In the drop-down list, you can select the default parameter template, the high-performance parameter template, or a custom parameter template in the current region as required. For details about the high-performance parameter template, see Introducing the High-Performance Parameter Template. If you use a custom parameter template when creating a DB instance, the specification-related parameters in the custom template will not be applied. Instead, the default values are used. For details, see What Parameters Should I Pay Attention to When Creating a DB Instance? After a DB instance is created, you can adjust its parameters as needed. For details, see Modifying Parameters of a DB Instance.
     Time Zone	You need to select a time zone for your instance based on the region hosting your instance. The time zone is selected during instance creation and cannot be changed after the instance is created.
     Table Name	Specifies whether table names are case sensitive. This option cannot be changed later. Case sensitive: Table names are case sensitive. Case insensitive: Table names are case insensitive and are stored in lowercase letters by default.
     Tag	Tags a DB instance. This parameter is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags. After a DB instance is created, you can view its tag details on the Tags tab. For details, see Tag Management.
     Quantity	You can buy DB instances in batches. The default value is 1. The value ranges from 1 to 10.

3. Confirm the settings.
   • If you need to modify your settings, click Previous.
   • If you do not need to modify your settings, click Submit.

4. Refresh the DB instance list and view the status of the DB instance. If the status changes from Creating to Available, it has been created successfully. You can manage the DB instance on the Instances page.

   The automated backup policy is enabled by default and cannot be disabled, and a full backup will be automatically created.

Follow-up Operations

After an instance is created, you can enter a description for it. For details, see Changing a DB Instance Description.

The default database port is 3306. You can change it after an instance is created. To ensure data and instance security, you are advised to change the database port in a timely manner. For details, see Changing a Database Port.

APIs

• Creating a DB Instance
• Querying DB Instances
• Deleting a Pay-per-Use DB Instance