Step 1: Create a DB Instance

Scenarios

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

The DB instance class and storage space you need depend on your processing power and memory requirements.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. On the Instance Management page, click Create DB Instance.
4. On the displayed page, configure information about your DB instance. Then, click Create Now.

   Table 1 Basic information

   Parameter	Description
   Region	The region where your RDS resources will be located. You can change it on the creation page, or go back to the Instance Management page and change it in the upper left corner. NOTE: Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Therefore, exercise caution when selecting a region.
   DB Instance Name	Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   DB Engine	Set to MySQL.
   DB Engine Version	For details, see DB Engines and Versions. Different DB engine versions are supported in different regions. You are advised to select the latest available version because it is more stable, reliable, and secure.
   DB Instance Type	Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created. An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability. Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
   Storage Type	Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be. High I/O: supports a maximum throughput of 150 MB/s. Ultra-high I/O: supports a maximum throughput of 350 MB/s.
   Time Zone	Select a time zone when you are creating a DB instance, and you can change it after the DB instance is created.

   Table 2 Instance specifications

   Parameter	Description
   Instance Class	Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS. For details about instance classes, see section DB Instance Classes. After a DB instance is created, you can change its instance class. For details, see section Changing a DB Instance Class.
   Storage Type	Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be. Ultra-high I/O: supports a maximum throughput of 350 MB/s.
   Storage Space (GB)	Contains the file system overhead required for inode, reserved block, and database operation. After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space. NOTE: Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

   Table 3 Network

   Parameter	Description
   VPC	A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide. If no VPC is available, RDS allocates a VPC to you by default. NOTICE: After the 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. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled. A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet CIDR block. After the DB instance is created, you can change the floating IP address.
   Security Group	Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance. If no security group is available or has been created, RDS 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 for security reasons. Keep this password secure. The system cannot retrieve it. After a DB instance is created, you can reset this password. For details, see section Resetting the Administrator Password.
   Confirm Password	Must be the same as Administrator Password.
   Parameter Template	Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same 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 delivered. Instead, the default values are used. back_log innodb_io_capacity_max max_connections innodb_io_capacity innodb_buffer_pool_size innodb_buffer_pool_instances You can modify the instance parameters as required after the DB instance is created. For details, see section Modifying Parameters.
   Enterprise Project	If the DB instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. You can also go to the ProjectMan console to create a project. For details about how to create a project, see the ProjectMan User Guide.

   Table 5 Batch creation

   Parameter

   Description

   Quantity

   RDS supports DB instance creation in batches. If you choose to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a standby DB instance will be created synchronously. If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.

   Table 6 Read replicas

   Parameter	Description
   Read Replica	By default, read replicas are named with "read" and two digits appended to the primary DB instance name. For example, if the primary instance name is instance-0001, the first read replica will be named instance-0001-read-01. The network and storage configurations are the same as those of the primary DB instance.
   Read Replica AZ	By default, the primary DB instance and read replicas are deployed in different AZs. You can choose AZs as required. NOTICE: Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.
   Instance Class	Refers to the CPU and memory of a DB instance.
   Read Replica Quantity	You can choose to create read replicas when you are creating a primary DB instance. After the primary DB instance is created, the system automatically triggers the creation of read replicas. You can create a maximum of five read replicas for each primary DB instance. If you intend to create primary/standby DB instances and set Read Replica Quantity to 1, a primary/standby DB instance and a read replica will be created.

   

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

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

6. To view and manage the DB instance, go to the Instance Management page.
   • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available. You can view the detailed progress and result of the task on the Task Center page.
   • The automated backup policy is enabled by default. After the DB instance is created, you can modify the automated backup policy. 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 section Changing a Database Port.