This topic describes how to create an ApsaraDB RDS for MariaDB instance in the ApsaraDB RDS console. You can also call an API operation to create an ApsaraDB RDS for MariaDB instance.
For more information, see Pricing, billable items, and billing methods.
You have an Alibaba Cloud account. For more information, see Sign up with Alibaba Cloud.
- Log on to the ApsaraDB RDS console.
- Configure the following parameters.
Parameter Description Billing Method
Note A maximum of 30 pay-as-you-go RDS instances are allowed per Alibaba Cloud account. To increase this quota, you must click here to submit a ticket.
- Subscription: A subscription instance is an instance that you can subscribe to for a specified period of time and pay for up front. Subscription billing is more cost-effective than pay-as-you-go billing. Therefore, we recommend that you select subscription billing with a longer commitment. You can receive larger discounts for longer subscription periods.
- Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. We recommend that you select pay-as-you-go billing for short-term use. If you no longer need your pay-as-you-go instance, you can release it to reduce costs.
Region The region to which the RDS instance belongs.
- After you confirm the purchase order, you cannot change the selected region.
- We recommend that you select a region that is in close proximity to the geographic location where your users reside. This allows you to increase the access speeds of your users.
- The RDS instance must reside in the same region as the ECS instance that you want to connect. If the RDS and ECS instances reside in different regions, these instances cannot communicate over an internal network. In this case, these instances must communicate over the Internet and therefore cannot deliver optimal performance.
Database Engine The database engine and version that the RDS instance runs. Select MariaDB. Only MariaDB 10.3 is supported.Note The available database engines and versions vary based on the selected region. Edition The edition of the RDS instance. Only the High-availability edition is supported. In this edition, the database system consists of one primary RDS instance and one secondary RDS instance. These instances work in the high-availability architecture.Note The available RDS editions vary based on the selected region and database engine version. For more information, see Overview of ApsaraDB RDS editions. Storage Type
- Enhanced SSD: This option represents an enhanced SSD of PL1.
- ESSD PL2: An enhanced SSD of PL2 delivers IOPS and throughput that are twice higher than those delivered by an enhanced SSD of PL1.
- ESSD PL3: An enhanced SSD of PL3 delivers IOPS that is 20 times higher than the IOPS delivered by an enhanced SSD of PL1. It also delivers throughput that is 11 times higher than the throughput delivered by an enhanced SSD of PL1. Enhanced SSDs of PL3 are suitable for workloads that require high I/O performance to process concurrent requests. Enhanced SSDs of PL3 are also suitable for workloads that require stable read/write latency.
For more information, see Storage types.
Zone of Primary Node and Zone of Secondary Node
A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs.
You can select the Single-zone Deployment or Multi-zone Development method.
- Single-zone Deployment: If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are the same.
- Multi-zone Development: This is the recommended deployment method. If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are different. This allows you to provide zone-level disaster recovery. You must manually specify the Zone of Primary Node and the Zone of Secondary Node.
- After the RDS instance is created, you can view information about the RDS instance and its secondary RDS instance on the Service Availability page.
- If you select the RDS Basic Edition, the database system consists of only one primary RDS instance and supports only the single-zone deployment method.
Note 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.
- General-purpose (Entry-level): belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
- Dedicated Instance (Enterprise-level): belongs to the dedicated instance family or the dedicated host instance family. A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the top configuration of the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources on the server where it is deployed.
- Dedicated: A dedicated cluster exclusively occupies all the resources on a VM or physical host. The permissions to manage hosts in a dedicated cluster can be authorized to you. This allows you to create multiple database instances on a host. For more information, see Add hosts.
Capacity The storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files. The storage capacity increases in increments of 5 GB.Note The dedicated instance family supports exclusive allocations of resources. Therefore, the storage capacity of each instance type with local SSDs in this family is fixed. For more information, see Primary instance types.
- Click Next: Instance Configuration.
- Configure the following parameters.
Parameter Description Network Type The network type of the RDS instance. Only the VPC network type is supported. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and better performance than the classic network. After you select the VPC network type, you must also specify the VPC and VSwitch of Primary Node parameters. If you select the Multi-zone Deployment method in the Basic Configurations step, you must specify both the VSwitch of Primary Node and VSwitch of Secondary Node parameters.Note The new RDS instance must have the same network type as the Elastic Compute Service (ECS) instance to which you want to connect. If both the RDS and ECS instances have the VPC network type, make sure that they reside in the same VPC. Otherwise, they cannot communicate over an internal network. Resource Group
- Click Next: Confirm Order.
- Confirm the settings in the Parameters section, specify the Purchase Plan parameter and the Duration parameter, read and select Terms of Service, and then click Pay Now to complete the payment. You must specify the Duration parameter only when the RDS
instance uses the subscription billing method. Note When you create a subscription RDS instance, we recommend that you select Auto-Renew Enabled. This relieves the need to manually renew the RDS instance on a regular basis. This also allows you to avoid interruptions to your workloads due to overdue payments.
On the ApsaraDB RDS homepage, click Instances in the left-side navigation pane, select the region where the RDS instance resides in the top navigation bar, and then find the RDS instance based on the Creation Time.
What to do next
After the RDS instance is created, you must specify whitelist settings and create accounts on the RDS instance. If you want to connect to the RDS instance over the Internet, you must also apply for a public endpoint. After you connect to the RDS instance, you can migrate data to the RDS instance. For more information, see the following topics:
- After I create an RDS instance, why does the ApsaraDB RDS console not respond and
why am I unable to find the created RDS instance?
This issue may occur due to the following reasons:
- The RDS instance does not reside in the selected region.
In the top navigation bar, select the region where the RDS instance resides. Then, you can find the RDS instance.
- The selected zone cannot provide the required number of resources.
Resources in zones are dynamically allocated. After you submit the purchase order, the selected zone may be unable to provide the required number of resources. As a result, the RDS instance cannot be created. In this case, we recommend that you select another zone and try again. If the RDS instance cannot be created, you can go to the Orders page in the Billing Management console to view the refunded fee.
- The RDS instance does not reside in the selected region.
- How do I authorize a RAM user to manage my RDS instance?
For more information, see Use RAM to manage ApsaraDB for RDS permissions.
- If my RDS instance resides in a VPC, how many private IP addresses does the instance
The number of private IP addresses that your RDS instance occupies varies based on the selected database engine and the selected RDS edition.
- MySQL 5.5, 5.6, 5.7, and 8.0 on RDS High-availability Edition (with local SSDs): 1
- MySQL 5.6, 5.7, and 8.0 on RDS Enterprise Edition (with local SSDs): 1
- MySQL 5.7 on RDS Basic Edition (with standard SSDs): 1
- MySQL 8.0 on RDS Basic Edition (with standard SSDs): 2
- MySQL 5.7 and 8.0 on RDS High-availability Edition (with standard or enhanced SSDs): 3
- MySQL 5.7 and 8.0 on RDS Enterprise Edition (with standard or enhanced SSDs): 1
|Create instance||Creates an ApsaraDB RDS instance.|