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

Operation Process

Preparations

1. Sign up for a HUAWEI ID and enable Huawei Cloud services.
2. Before purchasing DB instances, ensure that your account balance is sufficient. Top up your account if required.
3. For fine-grained permissions management on Huawei Cloud resources, use Identity and Access Management (IAM) to create a user or user group and grant it specific operation permissions. For details, see Creating a User and Granting Permissions.

Step 1: Buy an RDS for MySQL DB Instance

1. Go to the Buy DB Instance page.
2. On the Quick Config page, set basic parameters.
   

   Only mandatory parameters are provided on the Quick Config page. For more parameters, see Buy a DB Instance.

   The following configuration items are only for reference. Select right resources to match your workloads.

   Figure 1 Basic Settings
   

   Parameter	Example Value	Description
   Billing Mode	Pay-per-use	The 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.
   Region	CN-Hong Kong	The region where your resources are located. NOTE: Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Therefore, exercise caution when selecting a region.
   DB Engine Version	8.0	The database version.
   DB Instance Type	Primary/Standby	The architecture type of an instance. Primary/Standby: An HA architecture. In a primary/standby pair, each instance has the same instance class. When a primary instance is being created, a standby instance is provisioned along with it to provide data redundancy. The standby instance is invisible to you after being created.
   Instance Class	General-purpose | 2U | 4G	The vCPU and memory of an instance.
   Storage	Cloud SSD | 100GB	The storage space of an instance. It contains the system overhead required for inodes, reserved blocks, and database operation.
   Disk Encryption	Disable	Enabling disk encryption improves data security, but slightly affects the read and write performance of the database.

3. Complete advanced configurations.
   Figure 2 Additional Options
   

   Parameter	Example Value	Description
   VPC	vpc-default	The 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 and Subnet.
   Subnet	subnet-default	A subnet provides dedicated network resources that are logically isolated from other networks for network security.
   Security Group	default	It can enhance security by controlling access to RDS for MySQL from other services.
   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.
   Table Name	Case insensitive	Whether table names are case sensitive. Restoration may fail if the case sensitivity settings of table names on the source and target instances are different. The case sensitivity of table names for created RDS for MySQL 8.0 instances cannot be changed.
   Quantity	1	The number of instances to be created.

4. Click Buy.
5. Check the purchased DB instance.
   Figure 3 Instance successfully purchased
   

Step 2: Buy an ECS

1. Go to the Elastic Cloud Server console.
2. Check whether there is an Elastic Cloud Server (ECS) in the CN-Hong Kong region.
   • If there is a Linux ECS, see Buying a DB Instance and Connecting to It Using a MySQL Client.
   • If there is a Windows ECS, go to 4.
   • If there is no ECS, go to 3.
   Figure 4 ECS
   
3. Buy an ECS and select Windows as its OS.

   To download a MySQL client to the ECS, bind an EIP to the ECS. The ECS must be in the same region, VPC, and security group as the RDS for MySQL DB instance for mutual communications.

   For details about how to purchase a Windows ECS, see "Purchasing an ECS" in Elastic Cloud Server Getting Started.

4. On the ECS Information page, check the VPC of the ECS.

5. On the Overview page of the RDS for MySQL instance, check the VPC of the DB instance.
   Figure 5 Overview
   
6. Ensure that the ECS and RDS for MySQL instance are in the same region and VPC. Then go to Step 3: Test Connectivity and Install MySQL-Front.
   • If they are not in the same region, purchase another ECS or DB instance. The ECS and DB instance in different regions cannot communicate with each other. To reduce network latency, deploy your DB instance in the region nearest to your workloads.
   • If the ECS and DB instance are in different VPCs, change the VPC of the ECS to that of the DB instance. For details, see Changing a VPC.

Step 3: Test Connectivity and Install MySQL-Front

1. Log in to the ECS. For details, see Login Using VNC in the Elastic Cloud Server User Guide.
2. On the Instances page of the RDS console, click the DB instance name.
3. Choose Connectivity & Security from the navigation pane. In the Connection Information area, obtain the floating IP address and database port of the DB instance.
   Figure 6 Connection information
   
4. Open the cmd window on the ECS and check whether the floating IP address and database port of the DB instance can be connected.

   telnet 192.168.6.144 3306

   • If yes, network connectivity is normal.
   • If no, check the security group rules.
     • Check the outbound rules of the ECS security group. By default, all outgoing network traffic is allowed.
       If not, add an outbound rule for the floating IP address and port of the DB instance.

       Figure 7 ECS security group
       
     • If in the security group of the DB instance, there is no inbound rule allowing the access from the private IP address and port of the ECS, add an inbound rule for the private IP address and port of the ECS. For details, see Configuring a Security Group Rule.
5. Open a browser, and download and install the MySQL-Front tool on the ECS (version 5.4 is used as an example).

Step 4: Connect to the DB Instance Using MySQL-Front

1. Start MySQL-Front.
2. In the displayed dialog box, click New.
   Figure 8 Connection management
   
3. Enter the information of the DB instance to be connected and click Ok.
   Figure 9 Adding an account
   

   Table 1 Parameter description

   Parameter	Description
   Name	Name of the database connection task. If you do not specify this parameter, it will be the same as that configured for Host by default.
   Host	Floating IP address obtained in 3.
   Port	Database port obtained in 3. The default value is 3306.
   User	Name of the user who will access the DB instance. The default user is root.
   Password	Password of the account for accessing the DB instance.

4. In the displayed window, select the connection that you have created in 3 and click Open. If the connection information is correct, the DB instance will be connected.
   Figure 10 Opening a session
   

FAQs

What Should I Do If I Can't Connect to My RDS DB Instance?

Follow-up Operations

After logging in to the DB instance, you can create or migrate your databases.

• Creating a Database Using the Console
• Creating a Database Using an API
• Managing Databases Using DAS
• Migrating Data to RDS for MySQL