doc-exports/docs/taurusdb/umn/gaussdb_02_0004.html

Step 1: Create a DB Instance

Scenarios

This section describes how to create a DB instance on the management console.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Databases, click TaurusDB.
4. On the Instances page, click Create DB Instance.
5. On the displayed page, configure parameters about the DB instance specifications. Then, click Create Now.

   Table 1 Basic information

   Parameter	Description
   Region	A region where the tenant is located. You can change it 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 over a private network and you cannot change the region of a DB instance after creating the instance.
   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	TaurusDB V2.0
   Storage Type	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. With hardware and network infrastructure technologies, DL5-based instances maintain the same high availability (zero RPO in the 3-AZ deployment) as DL6-based instances. Although the peak performance of DL5-based instances may be a bit less than what you get with DL6-based instances, the cost per unit of capacity is a lot less. DL5-based instances are suitable for CPU-intensive sub-core business systems, or application modules that need to minimize costs.
   AZ Type	An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. 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 DB instances based on the longitude and latitude of the region hosting your DB instance. The time zone can be selected during DB instance creation and cannot be changed after the DB instance is created.

   Table 2 Specifications and storage

   Parameter	Description
   Instance Specifications	Refers to the CPU and memory of a DB instance. Different instance specifications support different numbers of database connections and maximum IOPS. After a DB instance is created, you can change its CPU and memory. For details, see Changing vCPUs and Memory of an Instance.
   CPU Architecture	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.
   Nodes	A TaurusDB instance supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time. After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating Read Replicas.
   Storage	Contains the system overhead required for inode, reserved block, and database operation. You do not need to specify storage space when creating a DB instance.

   Table 3 Network

   Parameter	Description
   VPC	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 on how to create a VPC, see "Creating a VPC" in the Virtual Private Cloud User Guide. If no VPC is available, TaurusDB allocates a VPC to you by default.
   Subnet	Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets are only valid for a given AZ. The Dynamic Host Configuration Protocol (DHCP) function must be enabled by default for subnets in which you plan to create DB instances. It cannot be disabled. You can select or search for a desired subnet from the drop-down list. A private IP address is automatically assigned when you create an instance. You can also enter a free private IP address in the subnet CIDR block.
   Security Group	Enhances security by controlling access to TaurusDB from other services. You need to add rules to a security group that enable you to connect to your DB instance. If no security group is available or has been created, TaurusDB 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?,()&$). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking. Keep this password secure. 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 5 Parameter template

   Parameter	Description
   Parameter Template	Contains engine configuration values that can be applied to one or more DB instances. You can modify the instance parameters as required after the DB instance is created. For details, see Parameter Template Management.
   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.

   Table 6 Tag

   Parameter	Description
   Tag	Tags a TaurusDB 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 tags on the Tags tab. For details, see Tags.

   Table 7 Batch instance creation

   Parameter	Description
   Quantity	TaurusDB allows you to create DB instances in batches. The default value is 1. The value ranges from 1 to 10. 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 as instance-0001, the second as instance-0002, and so on.

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

7. To view and manage DB instances, go to the Instances page.
   • During the creation process, the DB instance status is Creating. When the status of the created instance is Available, the DB instance can be used.
   • An automated backup policy is enabled by default. After the DB instance is created, you can modify this policy as required. An automated full backup is immediately triggered after a DB instance is created.
   • The default database port is 3306. After a DB instance is created, you can change its port.

     For details, see Changing a Database Port.

Parent topic: Connecting to a DB Instance over a Private Network