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. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
4. On the Instances page, click Create DB Instance.
5. On the displayed page, configure information about your DB instance. Then, click Create Now.

   Table 1 Basic Settings

   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 of the DB instance cannot be changed. Therefore, exercise caution when selecting the region where the instance is located.

   Table 2 Engine Options

   Parameter	Description
   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. 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. 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.
   Primary AZ/Standby AZ	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 select different AZs for your primary and standby instances for cross-AZ disaster recovery. The primary and standby instances can be deployed in different AZs.

   Table 3 Instance Configuration

   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 Space	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.
   Enable autoscaling	If the storage type is cloud SSD or extreme SSD, you can enable storage autoscaling. When the available storage drops to a specified threshold, autoscaling is triggered. Enable autoscaling: If you select this option, autoscaling is enabled. Trigger If Available Storage Drops To: If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered. Autoscaling Limit: The default value range is from 40 GB to 4,000 GB. The limit must be no less than the storage of the DB instance. NOTE: If you specify a read replica when creating a primary DB instance and enable storage autoscaling for the primary DB instance, storage autoscaling is also enabled for the read replica by default.
   Disk Encryption	Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%. Key Generation: indicates the method of generating a tenant key. Select one from the drop-down list. Key Name: indicates the tenant key. Select one from the drop-down list. After disk encryption is enabled, the following restrictions apply: If you enable disk encryption during instance creation, the disk encryption status and the key cannot be changed later. Enabling disk encryption will not encrypt backup data stored in Object Storage Service (OBS). Keep the key secure. Once the key is disabled, deleted, or frozen, your instance will be inaccessible and its data may not be restored.

   Table 4 Basic Settings

   Parameter	Description
   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.
   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 character types: 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.
   Confirm Password	Must be the same as Administrator Password.

   Table 5 Connectivity

   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 within all AZs of one Region. 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. 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. 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 6 Additional Options

   Parameter	Description
   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.
   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.
   Table Name	Specifies whether table names are case sensitive. The case sensitivity of table names (lower_case_table_names) for created RDS for MySQL 8.0 instances cannot be changed.
   Tag	Tags an RDS DB instance. This configuration 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 section Managing Tags.

   Table 7 Required Duration and Quantity

   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.

   After the configuration, click Price Calculator to view the RDS configuration fee.

   

   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 the DB instance, go to the Instances 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.
   • During the creation process, do not delete the selected VPC or subnet.
   • 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.