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.

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.

   Table 1 Basic information

   Parameter	Description
   Billing Mode	Select Pay-per-use.
   Region	A region where the DB instance is located.
   DB Instance Name	A name starts with a letter and consists of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   DB Engine	GaussDB(for MySQL)
   DB Engine Version	MySQL 8.0
   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.
   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 2 Specifications and storage

   Parameter	Description
   Instance Specifications	Different instance specifications support different numbers of database connections and maximum IOPS. For details, see Instance Specifications.
   CPU Architecture	The CPU architecture can be x86. Under a CPU architecture, you need to select vCPUs and memory of a DB instance.
   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.
   Storage Space (GB)	Contains the system overhead required for inode, reserved block, and database operation. Pay-per-use instances: You do not need to specify storage, which will be scaled dynamically based on the amount of data that needs to be stored, and is billed hourly on a pay-per-use basis.

   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. 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.
   Subnet	Improves network security by providing dedicated network resources that are logically isolated from other networks. 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.

   Table 4 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.
   Confirm Password	Must be the same as Administrator Password.

   Table 5 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"
   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 6 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.

   Table 7 Batch instance creation

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

3. Confirm the settings for the pay-per-use instance.
   • 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 instance status becomes Available, the instance can be used.
   • 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.