Buying a Yearly/Monthly DB Instance

• Basic configuration
  Figure 1 Basic configuration
  

  Table 1 Basic configuration

  Parameter	Description
  Billing Mode	Select Yearly/Monthly.
  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	Select TaurusDB V2.0 (MySQL-compatible).
  Kernel Version	DB kernel version. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History. NOTE: Specifying the kernel version when buying an instance is in the OBT phase. To use this function, submit a service ticket.
  DB Instance Type	Select Cluster or Single. 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 only contains one primary node. 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 recommended for development and testing of microsites, and small and medium enterprises, or for learning about TaurusDB.
  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
  Instance Specifications	TaurusDB is a cloud-native database that uses 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 an 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 yearly/monthly instance at once. 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 space ranges from 40 GB to 128,000 GB and must be a multiple of 10. After a DB instance is created, you can change its storage space. NOTE: If you want to create a DB instance with storage of at least 10 GB, submit a service ticket.
  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. If you purchase X GB storage billed on a yearly/monthly basis and Y GB storage billed on a pay-per-use basis, you will get (X + Y) GB backup space for free.
  DR Instance	If your instance is unavailable due to unknown community bugs, misoperations, or AZ faults, a DR instance can take over the services. Only single-node RDS for MySQL DR instances are supported. Enabling this parameter automatically creates a DR instance and adjusts the binlog settings when your instance is ready. DR instances cannot be enabled for single-node TaurusDB instances.
  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 your databases and data files. After TDE is enabled, you need to select the cryptographic algorithm AES256 or SM4 as needed. For details about TDE constraints, see Enabling TDE for a DB Instance. To enable TDE, submit a service ticket.

  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 a 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 with a 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 are only valid within a specific AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets where you plan to create DB instances 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 service ticket. IPv6 needs to be enabled for subnets where DB instances are located. If IPv6 is not enabled, enable it by following the instructions provided in Creating a Subnet for an Existing VPC. 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.
  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 5 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 buy a batch of instances at once, a 4-digit numerical suffix will be added to the instance names, starting with -0001. If you later make another batch purchase, the new instance names will be numbered first using any suffixes missing from the sequence of your existing instances, and then continuing on from where your last batch purchase left off. For example, a batch of 3 instances gets the suffixes -0001, -0002, and -0003. If you deleted instance 0002 and then bought 3 more instances, the new instances would get the suffixes -0002, -0004, and -0005. The names for instances created in batches must consist of 4 to 59 bytes. Only letters, digits, hyphens (-), and underscores (_) are allowed.
  Administrator Password	The default administrator account is root. The administrator password must consist of 8 to 32 characters and contain at least three types 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 an instance is created, you can reset this password. For details, see Resetting the Administrator Password.
  Confirm Password	Enter the administrator password again.

• Advanced settings
  Figure 6 Advanced settings
  

  Table 6 Database proxy

  Parameter	Description
  Database Proxy	This parameter is 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 service ticket. 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 (TP) 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 (TP): The primary node does not process write or 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	This parameter is only available for enterprise users. To use it, 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	A parameter template contains the configuration values of a database engine. The parameters can be applied to one or more instances of the same type. In the drop-down list, you can select the default parameter template (Default-TaurusDB V2.0), the high-performance parameter template (Default-TaurusDB V2.0-High Performance), or a custom parameter template in the current region as required. Default-TaurusDB V2.0 contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage space of an instance. Parameter values in the default template cannot be changed, but you can create a custom template with whatever values you require. Default-TaurusDB V2.0-High Performance is a set of optimized configuration parameters that aim to enhance the performance and reliability of database servers. The parameter settings in the template can be adjusted based on different application scenarios and hardware configurations. For details, see Introducing the High-Performance Parameter Template. You can select a custom parameter template and change the parameter values as required. The changes to parameter values in a custom parameter template are not applied to your instance until you apply the template to the instance. For details, see Applying a Parameter Template. If you select a custom parameter template when creating an 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 an 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	This parameter controls whether table names stored on disks are case sensitive when databases and tables are created. 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	This parameter tags a TaurusDB instance. It is optional. Adding tags helps you better identify and manage your instances. Each instance can have up to 20 tags. After an instance is created, you can click its name and view its tags on the Tags page. For details, see Tag Management.

• Required duration and quantity
  Figure 7 Required duration and quantity
  

  Table 7 Required duration and quantity

  Parameter	Description
  Required Duration	The system will automatically calculate the configuration fee based on the selected required duration. The longer the required duration is, the larger discount you will enjoy.
  Auto-renew	By default, this option is not selected. If you select this option, the auto-renewal cycle is determined by the selected required duration.
  Quantity	You can create instances in batches. The default value is 1. The value ranges from 1 to 10.

• If you need to modify your settings, click Previous.
• If you do not need to modify your settings, click Pay Now.

Yearly/Monthly instances are created only after you complete the payment.

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

• Basic configuration
  Figure 8 Basic configuration
  

  Table 8 Basic configuration

  Parameter	Description
  Region	Region where an instance is deployed. NOTE: You cannot change the region of an instance once it is purchased.

• Resource selection
  Figure 9 Resource selection
  

  Table 9 Resource selection

  Parameter	Description
  Compatible DB Engine	Select MySQL.
  Kernel Version	DB kernel version. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History. NOTE: Specifying the kernel version when buying an instance is in the OBT phase. To use this function, submit a service ticket.
  Instance Specifications	Select appropriate instance specifications to suit your business needs. Starter: for study and practice, small websites or applications, and developing and testing environments where cost-effectiveness is important Basic: for small and medium enterprises and Internet applications Professional: for medium and large enterprises in multimedia, gaming, and e-commerce
  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.
  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.

• Advanced settings
  Figure 10 Advanced settings
  
  Figure 11 Enterprise project
  

  Table 10 Advanced settings

  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.
  Administrator Password	The default administrator account is root. The administrator password must consist of 8 to 32 characters and contain at least three types 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 an instance is created, you can reset this password. For details, see Resetting the Administrator Password.
  Confirm Password	Enter the administrator password again.
  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 a TaurusDB instance is created, the VPC cannot be changed.
  Subnet	A subnet provides dedicated network resources that are logically isolated from other networks for network security. Subnets are only valid for a specific AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets in which you plan to create TaurusDB instances and cannot be disabled.
  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.
  Enterprise Project	This parameter is only available for enterprise users. To use it, 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	A parameter template contains the configuration values of a database engine. The parameters can be applied to one or more instances of the same type. In the drop-down list, you can select the default parameter template (Default-TaurusDB V2.0), the high-performance parameter template (Default-TaurusDB V2.0-High Performance), or a custom parameter template in the current region as required. Default-TaurusDB V2.0 contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage space of an instance. Parameter values in the default template cannot be changed, but you can create a custom template with whatever values you require. Default-TaurusDB V2.0-High Performance is a set of optimized configuration parameters that aim to enhance the performance and reliability of database servers. The parameter settings in the template can be adjusted based on different application scenarios and hardware configurations. For details, see Introducing the High-Performance Parameter Template. You can select a custom parameter template and change the parameter values as required. The changes to parameter values in a custom parameter template are not applied to your instance until you apply the template to the instance. For details, see Applying a Parameter Template. If you select a custom parameter template when creating an 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 an 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.
  Tag	This parameter tags a TaurusDB instance. It is optional. Adding tags helps you better identify and manage your instances. Each instance can have up to 20 tags. After an instance is created, you can click its name and view its tags on the Tags page. For details, see Tag Management.

• If you need to modify your settings, click Previous.
• If you do not need to modify your settings, click Pay Now.