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.

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 Pay-per-use.
   Region	Region where the DB 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 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	Select Primary/Standby or Single. 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 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. 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).
   Storage Type	DL6 The original Shared storage. The default storage type of GaussDB(for MySQL) instances created before July 2024 is Shared storage, while that of GaussDB(for MySQL) instances created after July 2024 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 storage type. It 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. Compared with DL6-based instances, although the peak performance of DL5-based instances may decrease, the cost per unit capacity is significantly reduced. DL5-based instances are suitable for CPU-intensive sub-core business systems or cost-effective application modules. For more information about storage types, see Storage Types.
   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: If your workloads require cross-AZ DR or are insensitive to cross-AZ latency, you are advised to deploy the primary node and read replicas in different AZs to achieve higher availability and 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 DB instance
   

   Table 2 Specifications and storage

   Parameter	Description
   Instance Specifications	GaussDB(for MySQL) is a cloud-native database that uses the shared storage. To ensure that DB instances run stably under high read/write pressure, GaussDB(for MySQL) controls the read/write peaks of DB instances based on instance specifications. For details about how to select specifications, see Performance White Paper. For more information about specifications, see Instance Specifications. After a DB instance is created, you can change its vCPUs and memory. For details, see Changing the vCPUs or Memory of a DB Instance or Node.
   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 primary/standby DB instances. By default, each DB instance contains a primary node and multiple read replicas. You can create up to 9 read replicas for a pay-per-use DB instance at a time. You can also add read replicas after a DB instance is created. 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 of a pay-per-use DB instance 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 TDE, submit an application by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console. TDE has certain constraints. For details, see Enabling TDE for a DB Instance.
   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.

   Figure 9 Purchase quantity
   

   Table 8 Purchase quantity

   Parameter	Description
   Quantity	You can buy DB 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. 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
• Deleting a Pay-per-Use DB Instance