This topic describes how to create an ApsaraDB RDS for MariaDB TX instance in the ApsaraDB RDS console. You can also create an ApsaraDB RDS for MariaDB TX instance by calling an API operation.

Prerequisites

You have an Alibaba Cloud account. For more information, see Sign up with Alibaba Cloud.

Procedure

  1. Go to the ApsaraDB RDS buy page.
  2. Select a billing method.
    • Subscription: A subscription instance is an instance for which you pay an upfront fee. For long-term use, we recommend that you select the Subscription billing method. If you select the subscription billing method, you must also specify the Duration parameter in the lower section of the page. The subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription periods.
    • Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. For short-term use, we recommend that you select the Pay-As-You-Go billing method. If you no longer need a pay-as-you-go RDS instance, you can release the instance to reduce costs.
    Note
    • You can create a pay-as-you-go RDS instance. After you confirm that the RDS instance that you created meets your business requirements, you can change the billing method of the RDS instance to subscription.
    • If you want to manage the host on which your RDS instance is deployed, you must select Dedicated Cluster (Subscription) to create a host. Then, you can create an RDS instance on the host.
  3. Configure the following parameters.
    Parameter Description
    Region The region where the RDS instance resides.
    • If your application is deployed on an Elastic Compute Service (ECS) instance, the RDS instance must reside in the same region as the ECS instance. For example, the RDS instance and the ECS instance can both reside in the China (Hangzhou) region. If the RDS instance and the ECS instance reside in different regions, they cannot communicate over an internal network and therefore they cannot deliver optimal performance.
    • If your application is deployed on an on-premises server or computer, we recommend that you select a region that is in close proximity to the on-premises server or computer.
    Database Engine The database engine and version that are run by the RDS instance. Select the MariaDB TX database engine. Only MariaDB 10.3 is supported.
    Note The available database engines and versions vary based on the region that you select.
    Edition The RDS edition of the RDS instance. Select High-availability. In RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance, which work in a high-availability architecture.
    Note The available RDS editions vary based on the region and database engine version that you select. For more information, see Overview of ApsaraDB RDS editions.
    Storage Type The type of storage medium that is used by the instance. ApsaraDB RDS for MariaDB TX supports enhanced SSDs (ESSDs), which come in three performance levels (PLs).
    • ESSD PL1: This is the basic PL of ESSDs.
    • ESSD PL2: An ESSD of PL2 delivers IOPS and throughput that are approximately twice higher than the IOPS and throughput delivered by an ESSD of PL1.
    • ESSD PL3: An ESSD of PL3 delivers IOPS that is up to 20 times higher than the IOPS delivered by an ESSD of PL1. An ESSD of PL3 also delivers throughput that is up to 11 times higher than the throughput delivered by an ESSD of PL1. ESSDs of PL3 are suitable for business scenarios in which highly concurrent requests must be processed with high I/O performance and at low read and write latencies.

    For more information, see Storage types.

    Zone

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. For example, the China (Hangzhou) region contains Zone H, Zone I, and Zone J. ApsaraDB RDS supports the following two deployment methods:

    • Multi-zone Deployment: The primary RDS instance and the secondary RDS instance reside in different zones to provide zone-disaster recovery. This is the recommended deployment method.
    • Single-zone Deployment: The primary RDS instance and the secondary RDS instance reside in the same zone.
    Note If you select the RDS Basic Edition, you can select only the Single-zone Deployment method.
    Instance Type The instance type of the RDS instance. Before you select an instance type, you must select an instance family.
    • General-purpose (Entry-level): 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 host.
    • Dedicated (Enterprise-level): A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host instance occupies all the CPU, memory, storage, and I/O resources on the host where the instance is deployed.
    Note For more information, see Primary ApsaraDB RDS instance types.
    Capacity The maximum amount of storage that is provisioned to store data files, system files, binary log files, and transaction files in the RDS instance. You can adjust the storage capacity at a step size of 5 GB.
    Note A dedicated RDS instance that uses local SSDs exclusively occupies the allocated resources, and its storage capacity varies based on the instance type. For more information, see Primary ApsaraDB RDS instance types.
  4. In the lower-right corner of the page, click Next: Instance Configuration.
  5. Configure the following parameters.
    Parameter Description
    Network Type The network type of the RDS instance. Select VPC. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and higher performance than the classic network. If you select the VPC network type, you must specify the VPC and VSwitch of Primary Node parameters. If you set the Deployment Method parameter in the previous step to Multi-zone deployment, you must also specify the VSwitch of Secondary Node parameter.
    Note The network type of the RDS instance must be the same as the network type of the Elastic Compute Service (ECS) instance that you want to connect. If the RDS instance and the ECS instance reside in VPCs, both instances must reside in the same VPC. If the RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.
    Resource Group The resource group to which the RDS instance belongs. You can retain the default resource group or select a custom resource group based on your business requirements.
  6. In the lower-right corner of the page, click Next: Confirm Order.
  7. Confirm the configuration of the RDS instance in the Parameters section, specify the Purchase Plan and Duration parameters, read and select Terms of Service, and then click Pay Now. You need to specify the Duration parameter only when you select the subscription billing method for the RDS instance.
    Note If you select the subscription billing method for the RDS instance, we recommend that you select Auto-Renew Enabled. This prevents interruptions to your workloads even if you forget to review the RDS instance.
  8. View the RDS instance.
    Go to the Instances page. In the top navigation bar, select the region where the RDS instance resides. Then, find the RDS instance based on the Creation Time. ApsaraDB RDS requires approximately 10 minutes to create an RDS instance.

What to do next

FAQ

  • After I create an RDS instance, why does the ApsaraDB RDS console not respond and why am I unable to find the RDS instance?

    This issue may occur due to the following reasons:

    • The region that you selected is not the region where the RDS instance resides.

      In the top navigation bar, select the region where the RDS instance resides. Then, you can find the RDS instance.

    • The zone that you selected cannot provide sufficient resources.

      Resources are dynamically allocated within zones. After you submit the purchase order, the zone that you selected may run out of resources. As a result, the RDS instance cannot be created. We recommend that you select a different zone and try again. If the RDS instance still cannot be created, you can go to the the Orders page in the Billing Management console to view the refunded fee.

  • How do I authorize a RAM user to manage my RDS instance?

    For more information, see Use RAM to manage ApsaraDB RDS permissions.

  • If my RDS instance resides in a VPC, how many private IP addresses does it have?

    The number of private IP addresses that your RDS instance has varies based on the database engine and RDS edition that are used.

    • 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 SSDs or ESSDs: 3
    • MySQL 5.7 and 8.0 on RDS Enterprise Edition with standard SSDs or ESSDs: 1

References