Step 1: Create a DB Instance

Scenarios

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 Database, click Relational Database Service.
4. On the Instances page, click Create DB Instance.
5. On that page, configure information about your DB instance. Then, click Create Now.
   • Basic information

     Table 1 Basic information

     Parameter	Description
     Region	Region where your resources are located. 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 (case-sensitive), 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. When creating an RDS for MySQL instance, select a proper DB engine version tailored to your workloads. You are advised to select the latest available version because it is more stable, reliable, and secure.
     DB Instance Type and AZ	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 less expensive than primary/standby DB instances. It is suitable for development and testing of microsites, and small and medium 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. Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s. Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
     Time Zone	You need to select a time zone for your instance based on the region hosting your instance. You can select a time zone during instance creation and change it later as needed.

   • Specifications and storage

     Table 2 Specifications and storage

     Parameter	Description
     Instance Class	Refers to the vCPU and memory of a DB instance. Different instance classes support different numbers of database connections and maximum IOPS. For details about instance classes, see RDS for MySQL Instance Classes. After a DB instance is created, you can change its instance class. For details, see Changing a DB Instance Class.
     Storage Space	Contains the system overhead required for inodes, reserved blocks, and database operation. After a DB instance is created, you can scale up its storage space. For details, see 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.
     Disk Encryption	Disable: Data stored in the disk is not encrypted. Enable: Enabling disk encryption improves data security, but slightly affects the read and write performance of the database. Key Name: indicates the tenant key. You can select an existing key or create a new one. NOTE: After an instance is created, the disk encryption status and the key cannot be changed. The backup data stored in OBS is not encrypted. After an instance is created, do not disable or delete the key that is being used. Otherwise, the database will be unavailable and data cannot be restored. For details about how to create a key, see the "Creating a CMK" section in the Data Encryption Workshop User Guide.

   • Network and database configuration

     Table 3 Network

     Parameter	Description
     VPC	A virtual network in which your RDS DB instances are located. A VPC can isolate networks for different workloads. You can select an existing VPC or create a VPC. For details about how to create a VPC, see "Creating a VPC" in Virtual Private Cloud User Guide. If no VPC is available, RDS 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. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you create RDS DB instances and cannot be disabled. IPv4 address: A floating IPv4 address is automatically assigned when you create a DB instance. You can also enter an unused floating IPv4 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. Ensure that the security group you select allows the client to access the 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. If the password you provide is regarded as a weak password by the system, you will be prompted to enter a stronger password. 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.
     Parameter Template	Contains engine configuration values that can be applied to one or more DB instances. If you intend to create a primary/standby DB pair, 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 Modifying Parameters of an RDS for MySQL Instance.
     Table Name	Specifies whether table names are case sensitive. The case sensitivity of table names for created RDS for MySQL 8.0 instances cannot be changed.
     Enterprise Project	If your account has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list.

   • Tags

     Table 5 Tags

     Parameter	Description
     Tag	Tags an RDS DB instance. This parameter is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 20 tags can be added for each DB instance. After a DB instance is created, you can click it and view its details on the Tags page. For details, see RDS for MySQL Tags.

   • Batch creation

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

   • Read replicas

     Table 7 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.
     Storage Type	Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the read/write speed can be. Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
     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. After a DB instance is purchased, the region cannot be changed. Therefore, exercise caution when selecting a region.
     Instance Class	Refers to the vCPU and memory of a read replica.
     Read Replica Quantity	You can create a maximum of five read replicas for each DB instance. After a DB instance is created, the system automatically triggers the creation of read replicas. If you intend to create primary/standby DB instances and set Read Replica Quantity to 1, a pair of primary/standby DB instances and a read replica will be created.

   Note

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

6. Confirm the 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 your DB instance, go to the Instances page.
   • When your DB instance is being created, the status is Creating. The status changes to Available after the instance is created. To view the detailed progress and result of the creation, go to the Task Center page.
   • The automated backup policy is enabled by default. You can change it after the DB instance is created. An automated full backup is immediately triggered once your DB instance is created.
   • The default database port is 3306. You can change it after a DB instance is created.

     For details, see Changing a Database Port.