Buying a Serverless DB Instance

Scenarios

The capacities of serverless DB instances automatically change based on application requirements.

This section describes how to create a serverless DB instance on the GaussDB(for MySQL) console.

Constraints

Currently, instances billed at a serverless billing can be purchased in the following regions:

• CN North-Beijing4
• CN East-Shanghai1
• AP-Singapore

Billing

For details, see Serverless Billing.

Prerequisites

• You have created a Huawei ID and enabled Huawei Cloud services.

• You can create an IAM user or user group on the IAM console and grant it specific operation permissions, to perform refined management on Huawei Cloud. For details, see Creating a User and Granting Permissions.
• Your account balance is not below zero.

Procedure

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

   Table 1 Basic information

   Parameter	Description
   Billing Mode	Select Serverless.
   Region	A region where the DB instance is located. You can change this on the creation page, or go back to the Instances page and change it in the upper left corner. NOTICE: Products in different regions cannot communicate with each other through a private network. After a DB instance is purchased, the region cannot be changed.
   DB Instance Name	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.
   DB Engine	GaussDB(for MySQL)
   DB Engine Version	MySQL 8.0
   DB Instance Type	Only primary/standby DB instances are supported. Primary/Standby: A primary/standby instance contains one primary node and up to seven read replicas. The primary node processes read and write requests, and the read replicas process only read requests. If the primary node becomes unavailable, GaussDB(for MySQL) automatically fails over to a read replica. Primary/standby instances apply to medium- and large-sized enterprises in the Internet, taxation, banking, and insurance sectors.
   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 ensure high reliability.
   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.

   Figure 2 Specifications and storage of a serverless DB instance
   

   Table 2 Specifications and storage

   Parameter	Description
   Compute Configuration	Currently, only Custom is supported.
   Compute Range	1 TCU is approximately equal to 1 vCPU and 2 GB of memory. Value range: 1 TCU to 32 TCUs
   Nodes	Total number of one primary node and read replicas you created for the instance. You can create up to 8 nodes at a time.
   Storage	It contains the system overhead required for inodes, reserved blocks, and database operations. Storage 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	GaussDB(for MySQL) 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.

   Figure 3 Network settings
   

   Table 3 Network

   Parameter	Description
   VPC	A dedicated virtual network where your instances are located. It isolates networks for different workloads to enhance security. GaussDB(for MySQL) allocates a default VPC (default_vpc) for your instance. You can also use an existing, new, or shared VPC and subnet. To use an existing VPC and subnet, select an existing VPC and subnet under the current account from the drop-down lists. To use a new VPC and subnet, create a VPC and subnet, and then select the VPC and subnet from the drop-down lists. For details about how to create a VPC and subnet, see "Creating a VPC and Subnet" in Virtual Private Cloud User Guide. To use a shared VPC and subnet, select a VPC and subnet that another account shares with the current account from the drop-down lists. With Resource Access Manager (RAM), you can share subnets in a VPC with one or more accounts so you can centrally manage resources in multiple accounts. This helps improve resource management efficiency and reduces O&M costs. For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide. NOTICE: After a DB instance is created, the VPC cannot be changed.
   Security Group	Enhances security by controlling access to GaussDB(for MySQL) from other services. When you select a security group, you must ensure that it allows the client to access instances. If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default. NOTE: To ensure subsequent database connections and access, click Add Inbound Rule to allow all IP addresses to access your DB instance through port 3306 and over ICMP. For details, see Configuring Security Group Rules.

   Figure 4 Proxy instance settings
   

   Table 4 Database proxy

   Parameter	Description
   Database Proxy	It is enabled by default. After the database proxy is enabled, you can use the IP address of a proxy instance to connect to your DB instance. NOTE: To use this function, submit an application by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. You can also create proxy instances after a DB instance is created. For details, see Step 1: Create a Proxy Instance.
   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: 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.

   Figure 5 Database settings
   

   Table 5 Database settings

   Parameter	Description
   Administrator	The default login name for the database is root.
   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. NOTICE: 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. Figure 6 Checking the password-related parameters 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	Must be the same as Administrator Password.

   Figure 7 Other information settings
   

   Table 6 Other information

   Parameter	Description
   Parameter Template	Contains engine configuration values that can be applied to one or more instances. In the drop-down list, you can view the default parameter template (Default-GaussDB-for-MySQL 8.0), high-performance parameter template (Default-GaussDB-for-MySQL 8.0-High Performance), and all custom parameter templates in the current region. You can select an appropriate parameter template as required. NOTICE: If you use a custom parameter template when creating a DB instance, the following specification-related parameters in the custom template are not applied. Instead, the default values are used. "innodb_buffer_pool_size" "innodb_log_buffer_size" "max_connections" "innodb_buffer_pool_instances" "innodb_page_cleaners" "innodb_parallel_read_threads" "innodb_read_io_threads" "innodb_write_io_threads" "threadpool_size" The value of innodb_parallel_select_count is determined by your instance specifications, instead of the parameter value you configured in the parameter template. The default value is OFF for instance with 16 vCPUs or less and ON for instances with more than 16 vCPUs. For more information about parameter templates, see Parameter Template Management. For more information about the high-performance parameter template, see Introducing the High-Performance Parameter Template. You can modify the instance parameters as required after a DB instance is created. For details, see Modifying Parameters of a DB Instance.
   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.
   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.

   Figure 8 Tag settings
   

   Table 7 Tags

   Parameter	Description
   Tag	(Optional) Tags a GaussDB(for MySQL) instance. 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.

   

   The performance of a DB instance depends on its configuration. Hardware configuration items include the instance specifications, storage type, and storage space.

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

4. To view and manage instances, go to the Instances page.
   • During the creation process, the instance status is Creating. After the status of the instance is Available, you can use the instance.
   • Automated backup is enabled by default during instance creation. After your instance was created, the backup policy cannot be disabled and a full backup will be automatically created.
   • After the instance is created, you can confirm the DB instance type on the Instances page.
   • After the instance is created, you can add a description.
   • The default database port is 3306, but you can change it after instance creation is complete. To ensure data and instance security, change the database port immediately after the instance is created.

     For details, see Changing a Database Port.

APIs

• Creating a DB Instance
• Querying DB Instances