This topic describes how to create an ApsaraDB RDS for MySQL in the ApsaraDB for RDS console. You can also create an ApsaraDB RDS for MySQL instance by calling an API operation.
Create an RDS instance in the original ApsaraDB for RDS console
- Log on to the original ApsaraDB for RDS console.
- Select a billing method.
- Pay-As-You-Go: A pay-as-you-go instance is charged at an hourly rate based on your actual resource usage. We recommend that you select pay-as-you-go billing for short-term use. You can reduce costs by releasing your pay-as-you-go instance after you no longer need it.
- Subscription: You must pay the subscription fee when you create an instance. We recommend that you select subscription billing with a longer commitment because it is more cost-effective than pay-as-you-go billing. You receive larger discounts for longer subscription periods.
- Configure the following parameters.
Parameter Description Region
The region where the RDS instance resides. After the RDS instance is created, you cannot change its region.
- To maximize your access speed, we recommend that you select a region in close proximity to the geographic location where you reside.
- Make sure that the RDS instance is created in the same region as the ECS instance that you want to connect. If the RDS and ECS instances reside in different regions, they cannot communicate over an internal network and therefore cannot deliver optimal performance.
The resource group to which the RDS instance belongs.
The database engine used by the RDS instance. Select MySQL.Note The database engines available vary depending on the region you select.
The database engine version used by the RDS instance. The following MySQL versions are supported: 5.5, 5.6, 5.7, and 8.0.Note The database engine versions available vary depending on the region you select.
Note The RDS editions available vary depending on the database engine version you select. For more information, see RDS editions overview.
- Basic: The database system consists of only one instance. Computing is separated from storage to increase cost-effectiveness.
- High-availability: The database system works in the classic high-availability architecture and consists of one primary instance and one secondary instance.
- Enterprise Edition: The database system consists of one primary instance and two secondary instances. The primary and secondary instances are located in three different zones within the same region to provide financial-level reliability. The Enterprise Edition is only available in four regions: China (Hangzhou), China (Shanghai), China (Shenzhen), and China (Beijing).
- Local SSD: A local SSD is a storage device in the server node where the database engine resides. With local SSDs, computing is closer to data to reduce the I/O latency.
- Standard SSD: A standard SSD is an elastic block storage device based on the distributed storage architecture. With standard SSDs, computing is separated from storage.
- Enhanced ESSD: An ESSD is an ultra-high performance disk provided by Alibaba Cloud based on the new generation of distributed block storage architecture. It integrates 25 Gigabit Ethernet and RDMA technologies to reduce latency and deliver up to 1 million random IOPS.
For more information, see Storage types.
The zone to which the RDS instance belongs. A zone is an isolated geographic area within a region. There are no differences between zones in the same region. You can create the primary and secondary instances of your database system in the same zone or in different zones.
If your database system spans multiple zones, it can provide zone-level disaster recovery.
- Classic Network: the traditional type of network.
- VPC: A VPC is an isolated virtual network with higher security and better performance than a classic network.
Note Make sure that the RDS instance has the same network type as the ECS instance you want to connect. If the RDS and ECS instances have different network types, they cannot communicate over an internal network.
CPU and Memory
Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see Primary instance types.
ApsaraDB for RDS provides the following instance families:
- General-purpose instance: A general-purpose instance occupies the exclusive memory and I/O resources allocated to it, but shares CPU and storage resources with the other general-purpose instances on the same server.
- Dedicated instance: A dedicated instance occupies the exclusive CPU, memory, storage, and I/O resources allocated to it.
- Dedicated host: The dedicated host instance family is the top configuration of the dedicated instance family. A dedicated host instance occupies all CPU, memory, storage, and I/O resources on the server where it resides.
For example, "8 Cores, 32 GB (General-purpose instance)" is a general-purpose instance type, "8 Cores, 32 GB (Dedicated Instance)" is a dedicated instance type, and "30 Cores, 220 GB (Dedicated Host) is a dedicated host instance type.
The storage capacity of the RDS instance to store data files, system files, binary log files, and transaction files.
- Specify Duration and Quantity, and click Buy Now. Note that you only need to specify Duration if you create a subscription instance.
- If you create a subscription instance, you can select Auto-renewal. The system automatically renews your subscription based on the duration you specify. For example, if you create a three-month subscription instance with Auto-renewal selected, you are charged a three-month subscription fee for each automatic renewal.
- If you create a subscription instance, you can click Add to Cart to add it to the shopping cart. Then, you can click Cart later to pay for the subscription instance.
- On the Order Confirmation page, confirm the instance configuration, read and select Product Terms of Service, and click Pay Now.