Buying a DB Instance and Connecting to It Using MySQL-Front

• Basic configuration
  Figure 1 Basic configuration
  

  Table 1 Basic configuration

  Parameter	Example	Description
  Billing Mode	Pay-per-use	Billing mode of an instance. Yearly/Monthly: A prepaid billing mode in which you pay for resources before using it. Bills are settled based on the subscription period. The longer the subscription, the bigger the discount. This mode is a good option for long-term, stable services. Pay-per-use: A postpaid billing mode. You pay as you go and just pay for what you use. The DB instance usage is calculated by the second but billed every hour. This mode allows you to adjust resource usage easily. You neither need to prepare for resources in advance, nor end up with excessive or insufficient preset resources. Serverless: The instance capacities automatically change based on application requirements. You can start using the DB instance first and then pay as you go.
  Region	CN-Hong Kong	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	Example	Description
  DB Engine Version	TaurusDB V2.0	DB engine and version.
  Kernel Version	2.0.60.241200	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	Create new	How an instance is created.
  Edition Type	Enterprise	Enterprise Edition is an enterprise-grade cloud-native database with high scalability and performance. It is fully compatible with open-source MySQL 8.0. It decouples compute from storage and uses Huawei-developed Data Function Virtualization (DFV), which scales to up to 128 TB per instance. A failover can be complete within seconds. High-value capabilities such as read/write splitting, operator pushdown, a serverless framework, and HTAP are also supported. It provides the high availability and superior performance of a commercial database at the price of an open-source database.
  DB Instance Type	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.
  AZ Type	Multi-AZ	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.

• Instance options
  Figure 3 Instance specifications
  

  Table 3 Instance specifications

  Parameter	Example	Description
  Instance Specifications	Dedicated 2 vCPUs | 4 GB	vCPUs and memory of an instance.
  CPU Architecture	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.
  Nodes	2	This parameter is mandatory for cluster and multi-primary instances.
  Storage	-	It contains the system overhead required for inodes, reserved blocks, and database operations.
  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	Disabled	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.

  Figure 4 Network
  

  Table 4 Network

  Parameter	Example	Description
  VPC	default_vpc	Virtual network in which your instance is located. A VPC can isolate networks for different workloads. If no VPC is available, click Create VPC. After a VPC is created, click . For details, see Creating a VPC with a Subnet. NOTICE: After the TaurusDB instance is created, the VPC cannot be changed.
  Subnet	default_subnet	A subnet provides dedicated network resources that are logically isolated from other networks for network security.
  Security Group	default	A security group enhances security by controlling access to TaurusDB from other services.

  Figure 5 Setting an administrator password
  

  Table 5 Database configuration

  Parameter	Example	Description
  DB Instance Name	TaurusDB-985e	DB instance name.
  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. 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
  Figure 6 Advanced settings and required quantity
  

  Table 6 Advanced settings and required quantity

  Parameter	Example	Description
  Enterprise Project	default	If your account has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. For more information about enterprise projects, see Enterprise Management User Guide.
  Parameter Template	Default-TaurusDB V2.0	Contains engine configuration values that can be applied to one or more instances.
  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	Case insensitive	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.
  Quantity	1	You can buy DB instances in batches. The default value is 1. The value ranges from 1 to 10.

telnet private_IP_address port

If the message "command not found" is displayed, install the Telnet tool based on the OS used by the ECS.

• If the ECS can connect to the DB instance, no further action is required.
• If the ECS cannot connect to the DB instance, check the security group rules.
  • If in the security group associated with the ECS, there is no outbound rule with Destination set to 0.0.0.0/0 and Protocol & Port set to All, add the private IP address and port of the DB instance to the outbound rules.
  • Add the private IP address and port of the ECS to the inbound rules in the security group associated with the DB instance.