All Products
Search
Document Center

ApsaraDB RDS:Create an ApsaraDB RDS for MariaDB instance

Last Updated:Dec 02, 2025

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

Prerequisites

A Resource Access Management (RAM) user must have the AliyunRDSFullAccess and AliyunBSSOrderAccess permissions to create an RDS instance. For more information about how to grant permissions, see Authorize resources to a RAM user.

Procedure

  1. Go to the ApsaraDB RDS instance creation page.

  2. Select a Billing Method.

    Billing method

    Recommendation

    Benefit

    Subscription

    For long-term use, select Subscription (one-time payment).

    Subscription is more cost-effective than pay-as-you-go. Longer subscription durations offer greater discounts.

    Pay-as-you-go

    For short-term use, select Pay-as-you-go (hourly billing).

    You can create a pay-as-you-go instance first and then convert it to subscription after you confirm that it meets your requirements.

    Release the instance at any time to stop billing.

    Note

    View the price in the lower-right corner of the page. The final price is calculated after you complete the configuration.

  3. Select the Region where you want to create the RDS instance.

    Create the RDS instance in the same region as your ECS instance to ensure optimal performance.

    Note
    • You cannot change the region after you purchase an RDS instance. Make sure the RDS instance is in the same region as the ECS instance to enable service interconnection.

    • If you connect from a device other than an ECS instance, select a region close to your device and connect using the public endpoint.

  4. Select the database Database Engine and Storage Type.

    Note
    • The Edition is set to High-availability Edition. This edition includes a primary node and a secondary node in a classic high availability architecture. It is suitable for production environments.

    • The Product Type is set to Standard.

    1. Select the Database Database Engine.

      Select MariaDB.

    2. Select a Storage Type. For more information, see Storage types.

      Item

      ESSD

      Scalability

      • Up to 32 TB.

      • No transient connections occur during storage capacity expansion.

      • Upgrade, downgrade, add, or remove nodes in minutes.

      • Supports automatic storage expansion.

      Performance

      • PL1<PL2<PL3

      • A PL2 ESSD delivers up to 2 times the IOPS and throughput of a PL1 ESSD.

      • A PL3 ESSD delivers up to 20 times the IOPS and 11 times the throughput of a PL1 ESSD.

      Backup

      • Backups complete in minutes or seconds.

      • The highest backup frequency is once every 15 minutes.

      Note

      Select Cloud Disk Encryption for additional data protection. For more information, see Disk encryption.

  5. Configure the instance network. The network type is set to VPC.

    1. Select a VPC. We recommend selecting the same VPC as your ECS instance. Services in different VPCs cannot connect to each other over an internal network.

    2. Specify whether to Add to Whitelist. If you add the CIDR block, ECS instances in the same VPC can access the RDS instance.

      Note

      If you select No, you can manually configure a whitelist after the instance is created. For more information, see Configure a whitelist.

  6. Select the zone, vSwitch, network, and Deployment Method for the instance.

    • Zone

      • There is no functional difference between zones in the same region.

      • An ECS instance achieves better performance when accessing an RDS instance in the same zone. The performance difference is minor if they are in different zones within the same region.

    • vSwitch

      Select an existing vSwitch or click Create vSwitch. For information about parameter configurations, see Create and manage a vSwitch.

    • Deployment method

      • Multi-zone Deployment (Recommended): The primary and secondary nodes are deployed in different zones within the same region. This provides cross-zone disaster recovery.

        If you select Deployment Method: Multi-zone Deployment, you must also select the Zone and Network of Primary Node and Zone and Network of Secondary Node.

      • Single-zone Deployment: The primary and secondary nodes are deployed in the same zone.

  7. Select an Instance Type.

    1. Select a Category (General-purpose or Dedicated).

      Category

      Description

      Features

      General-purpose Instance Types

      • Shared memory and I/O

      • Dedicated CPU and storage

      Low price, cost-effective

      Dedicated Instance Types

      Dedicated CPU, memory, storage, and I/O

      Note

      Dedicated Host is the top-tier configuration of the Dedicated category. It exclusively occupies all CPU, memory, storage, and I/O resources of a physical server.

      Better and more stable performance

      Note

      The Basic Edition does not support dedicated instance types.

    2. Select the required specifications (CPU cores and memory). For a list of specifications, see Instance types.

  8. Select the Storage Capacity.

    The available storage capacity range depends on the instance type and storage type you selected.

    You can adjust the storage capacity in increments of at least 5 GB.

  9. Optional. If you set the Billing Method parameter to Subscription, configure the Subscription Duration parameter in the upper-right corner of the page.

    Alibaba Cloud provides lower prices for longer subscription durations. You can move your pointer over View Details next to the Price to view the details.

  10. Set the custom parameters. You can use the default values if you do not have specific requirements.

    Parameter

    Description

    Port

    The port can be initialized. Value range: 1000 to 5999.

    Release Protection

    For pay-as-you-go instances, you can enable Release Protection to prevent accidental release. For more information, see Enable or disable release protection.

    Resource Group

    Select the default resource group or a custom resource group to help manage your instances.

    Instance Name

    Specify a custom name to easily identify the instance.

    Tags

    Use tags to classify and manage instances. For more information, see Filter instances by tag.

    Privileged Account

    Create a privileged account when you create the RDS instance. Each instance can have only one privileged account. The privileged account cannot be deleted.

  11. In the upper-right corner of the page, select the Quantity of instances to purchase.

    The default is 1. You can purchase up to 20 instances at a time. Select the required quantity.

  12. Confirm the order information, quantity, and subscription duration (for subscription instances only). Click Confirm Order and complete the payment. The console displays a Payment successful or Service activated message.

    Note

    For subscription instances, select Enable Auto-renewal to prevent service disruptions due to a missed renewal payment.

    If you purchase by month, the auto-renewal cycle is one month. If you purchase by year, the auto-renewal cycle is one year. The cycle specified in the order takes precedence. You can cancel auto-renewal at any time. For more information, see Renew an expired resource and Auto-renewal.

  13. View the instance.

    Go to the Instances page. In the top navigation bar, select the region of the instance. Find the new instance by its Creation Time.

    Note

    Instance creation takes about 1 to 5 minutes. Refresh the page to view the status.

What to do next

FAQ

How do I view the total number of RDS instances within my Alibaba Cloud account?

Log on to the ApsaraDB RDS console. On the Overview page, you can view the total number of RDS instances that run different database engines within your Alibaba Cloud account. On this page, you can also view the regions in which the RDS instances are created and the number of running RDS instances in each region.

image

After I create an RDS instance, why am I unable to find the RDS instance?

Possible cause

Description

Suggestion

Incorrect region

The RDS instance does not reside in the region that you selected in the top navigation bar of the ApsaraDB RDS console.

In the top navigation bar, select the region in which the RDS instance resides.

Insufficient resources

The zone that you selected cannot provide sufficient resources.

If the RDS instance cannot be created, you can go to the Orders page in the Billing Management console to view the refunded fees.

Select a different zone and try again.

RAM policies that do not allow users to create unencrypted RDS instances

RAM policies that do not allow users to create unencrypted RDS instances are attached to a RAM user.

  • If you use the credentials of the RAM user to create an RDS instance that uses local disks, the RDS instance cannot be created. When you create an RDS instance that uses local disks, you cannot enable cloud disk encryption.

  • If you use the credentials of the RAM user to create an RDS instance that uses cloud disks and you do not enable cloud disk encryption for the RDS instance, the RDS instance cannot be created.

For more information, see Use RAM policies to manage the permissions of RAM users on ApsaraDB RDS instances.

When you create an RDS instance, select the standard SSD or ESSD storage type, select Cloud Disk Encryption, configure the Key parameter, and then try again.

References