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 TaurusDB console.
Constraints
Serverless DB instances are only available in the following regions:
- CN North-Beijing4
- AP-Singapore
- ME-Riyadh
Billing
For details, see Serverless Billing.
Prerequisites
- 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 TaurusDB Permissions.
- Your account balance is not below zero.
Procedure
- Go to the Buy DB Instance page.
- On the displayed Custom Config page, configure required information and click Next.
- Basic configuration
Figure 1 Basic configuration
Table 1 Basic configuration Parameter
Description
Billing Mode
Select Serverless.
Region
Region where an instance is deployed.
NOTE:You cannot change the region of an instance once it is purchased.
- Resource selection
Figure 2 Resource selection
Table 2 Resource selection Parameter
Description
DB Engine Version
Select TaurusDB V2.0.
Kernel Version
DB kernel version. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History.
NOTE:- To specify the kernel version when buying an instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
- To buy a multi-primary instance, select kernel version 2.0.45.230950 or 2.0.57.240900.
Creation Method
Select Create new.
DB Instance Type
Only primary/standby instances are supported.
A primary/standby instance billed on a serverless basis can contain 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, TaurusDB 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 achieve higher availability and reliability. It is suitable for workloads that require cross-AZ DR or are insensitive to cross-AZ latency.
- Instance options
Figure 3 Specifications and storage
Table 3 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
TaurusDB 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.
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 the cryptographic algorithm AES256 or SM4 as needed.
NOTE:- To use TDE, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
- For details about TDE constraints, see Enabling TDE for a DB Instance.
Figure 4 NetworkTable 4 Network Parameter
Description
VPC
A dedicated virtual network where your instance is located. It isolates networks for different workloads to enhance security.
TaurusDB allocates a default VPC (default_vpc) for your instance. You can also use an existing, new, or shared VPC.
- To use an existing VPC, select an existing VPC under the current account from the drop-down list.
- To use a new VPC, create a VPC, and then select the VPC from the drop-down list.
For details about how to create a VPC, see Creating a VPC and Subnet in Virtual Private Cloud User Guide.
- To use a shared VPC, select a VPC that another account shares with the current account from the drop-down list.
With Resource Access Manager (RAM), you can share subnets in a VPC with one or more accounts, so you can easily configure and manage multiple accounts' resources at low costs.
For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide.
NOTICE:After a TaurusDB instance is created, the VPC cannot be changed.
Subnet
A subnet provides dedicated network resources that are logically isolated from other networks for network security. Subnets take effect only within an AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets where DB instances are located and cannot be disabled.
TaurusDB supports both IPv4 and IPv6.
- IPv4
A private IPv4 address is automatically assigned when you create a DB instance. You can also enter an idle private IPv4 address within the subnet CIDR block. After the DB instance is created, the private IPv4 address can be changed.
- IPv6
IPv6 addresses are used to deal with IPv4 address exhaustion. To enable IPv6, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
You can create a DB instance that uses a private IPv6 address only when its specifications support IPv6. Instance specifications supporting IPv6 vary depending on regions and AZs. Whether instance specifications support IPv6 is displayed on the console after a region and an AZ are selected.
IPv6 needs to be enabled for subnets where TaurusDB instances are located. If IPv6 is not enabled, enable it by following the instructions provided in Creating a VPC and Subnet.Figure 5 Enabling IPv6 for a subnet
NOTE:Instances using IPv4 and IPv6 cannot be in the same subnet. After IPv6 is enabled, if you want to create an instance using IPv4, you need to select an IPv4 subnet.
Security Group
A security group enhances security by controlling access to TaurusDB from other services. When you select a security group, you must ensure that it allows the client to access DB instances.
If no security group is available or has been created, TaurusDB allocates a security group to your DB instance by default.
NOTE:To ensure subsequent database connection and access, you need to allow all IP addresses to access your DB instance through port 3306 and over ICMP. If the port and protocol are not enabled for the selected security group, click Add Inbound Rule as prompted and complete the configuration in the displayed dialog box.
For details, see Configuring Security Group Rules.
Figure 6 Setting an administrator passwordTable 5 Database configuration Parameter
Description
DB Instance Name
The name must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), 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.
NOTE:To use Chinese characters, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
Administrator Password
The default administrator account is root.
The 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.
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
Enter the administrator password again.
- Advanced settings and required quantity
Figure 7 Advanced settings and required quantity
Table 6 Advanced settings Parameter
Description
Database Proxy
Enabled by default. After a proxy instance is created, you can use the proxy address to connect to your DB instance.
NOTE:- To create a proxy instance when buying a DB instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
- You can also create proxy instances after buying a DB instance. For details, see Creating a Proxy Instance for Read/Write Splitting.
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: Write requests are not forwarded to any node. 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.
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.
Parameter Template
Contains engine configuration values that can be applied to one or more instances.
In the drop-down list, you can select the default parameter template, the high-performance parameter template, or a custom parameter template in the current region as required. You can select an appropriate parameter template as required.
For more information about parameter templates, see Parameter Management. For more information about the high-performance parameter template, see Introducing the High-Performance Parameter Template.
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_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 adjust its parameters as needed. For details, see Modifying Parameters of a DB Instance.
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 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.
Tag
Tags a DB instance. This parameter is optional. 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.
Quantity
You can buy DB instances in batches. The default value is 1. The value ranges from 1 to 10.
The performance of a DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.
- Basic configuration
- Confirm your specifications.
- If you need to modify your settings, click Previous.
- If you do not need to modify your settings, click Submit.
- To view and manage DB 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, and 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot