Buying a Pay-per-Use DB Instance

Scenarios

This section describes how to create a pay-per-use DB instance on the GaussDB(for MySQL) console.

Billing

After you purchase a pay-per-use DB instance, you will be billed for resources you actually use. For more information, see Pay-per-Use 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, select Pay-per-use for Billing Mode, configure required information, and click Next.
   Figure 1 Basic information
   

   Table 1 Basic information

   Parameter	Description
   Billing Mode	Select Pay-per-use.
   Region	Region where the instance is deployed NOTICE: Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. For lower network latency and quicker resource access, select the nearest region. You cannot change the region of a DB instance once it is purchased.
   DB Instance Name	The instance name must start with a letter and consist of 4 to 64 characters. Only letters, 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.
   DB Engine	GaussDB(for MySQL)
   DB Engine Version	MySQL 8.0
   DB Instance Type	Primary/standby and single instance types are supported. Primary/Standby: A primary/standby instance contains one primary node and up to 15 read replicas. The primary node processes read and write requests, and 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. Single: A single-node instance contains only one primary node and there are no read replicas. Single-node instances do not involve data synchronization of 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 GaussDB(for MySQL). NOTE: The parameter DB Instance Type is displayed only after you have permissions for purchasing single-node instances.
   Storage Type	DL6 The shared storage is the default storage type for GaussDB(for MySQL) instances created before July 2024. DL6-based instances achieve zero RPO with a 3 AZ deployment and deliver better performance and higher peak throughput. Applicable Scenario: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 The new storage type uses Huawei Cloud's hardware and network infrastructure technologies, ensuring that DL5-based instances maintain the same high availability as DL6-based instances with 3 AZs and zero RPO. Although the peak performance may decrease, the cost per unit capacity is significantly reduced. Applicable Scenario:CPU-intensive sub-core business systems or cost-effective application modules. For more information about storage types, see Storage Type.
   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 pay-per-use instance
   

   Table 2 Specifications and storage

   Parameter	Description
   Instance Specifications	For details about the specifications supported by the GaussDB(for MySQL), see Instance Specifications. GaussDB(for MySQL) is a cloud-native database that uses the shared storage. To ensure service stability in high read/write pressure, the system controls the read/write peaks of DB instances based on instance specifications. For details about how to select specifications, see Performance White Paper. After a DB instance is created, you can change its vCPUs and memory.
   CPU Architecture	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 Internet enterprises needing cost-effective, secure, and reliable cloud services.
   Nodes	Total number of one primary node and read replicas you created for the instance. You can create up to 9 read replicas for a pay-per-use instance at a time. After a DB instance is created, you can add read replicas based on service requirements. Up to 15 read replicas can be created for a DB instance. For details, see Creating a Read Replica.
   Storage	Contains the system overhead required for inode, reserved block, and database operation. 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.
   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 a cryptographic algorithm AES256 or SM4 as needed. NOTE: To use this function, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. For details about TDE constraints, see Enabling TDE.
   Backup Space	GaussDB(for MySQL) provides free backup storage equal to the amount of your used storage space. 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
   

   Table 3 Network

   Parameter	Description
   VPC	Indicates a dedicated virtual network in which your DB instances are located. It isolates networks for different services. You can select an existing VPC or create a VPC. For details about how to create a VPC, see Creating a VPC. If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default. NOTICE: After a DB instance is created, the VPC cannot be changed. A subnet provides dedicated network resources that are logically isolated from other networks for network security. A private IP address is automatically assigned when you create a DB instance. You can also enter an idle private IP address in the subnet CIDR block. NOTE: Currently, GaussDB(for MySQL) does not support IPv6.
   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.

   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 a service ticket by choosing Service Tickets > Create Service Ticket. You can also create proxy instances after purchasing a DB instance. For details, see 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.

   Table 5 Database configuration

   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. 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.

   Table 6 Parameter template

   Parameter	Description
   Parameter Template	Contains engine configuration values that can be applied to one or more instances. You can modify the instance parameters as required after the instance is created. 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. After a DB instance is created, you can change the parameter template based on service requirements. For details, see Modifying a Parameter Template.
   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.

   Table 7 Tags

   Parameter	Description
   Tag	This parameter is optional. Adding tags helps you better identify and manage your DB instances. A maximum of 20 tags can be added for each instance. After a DB instance is created, you can view its tag details on the Tags tab. For details, see Managing Tags.

   Table 8 Batch instance creation

   Parameter	Description
   Quantity	You can create instances in batches. The default value is 1. The value ranges from 1 to 10.

   If you have any questions about the price, click Pricing details at the bottom of the page.

   

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

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. 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.

     For details, see Changing a Database Port.

     

     To ensure data and instance security, change the database port immediately after the instance is created.

APIs

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