All Products
Search
Document Center

ApsaraDB RDS:Step 1: Create and configure an ApsaraDB RDS for MySQL instance

Last Updated:Mar 30, 2026

ApsaraDB RDS for MySQL (RDS for MySQL) is a managed database service that runs on dedicated cloud servers. This guide walks you through creating an instance, a database, and a privileged account from the console — the three resources you need before connecting to your database.

Cost Varies by instance settings. View pricing details.
What you'll create An RDS for MySQL instance, one database, and one privileged account
For a quick start or trial, use your Alibaba Cloud account directly to avoid permission issues.

Prerequisites

Before you begin, ensure that you have:

  • An Alibaba Cloud account

  • (Optional) An Elastic Compute Service (ECS) instance, if you plan to connect to RDS over the internal network

Step 1: Create an RDS for MySQL instance

  1. Go to the RDS buy page.

  2. Configure the parameters in the following table. Leave all other settings at their default values.

    Parameter Suggested value Description
    Billing Method Pay-as-you-go Choose based on your usage pattern. Pay-as-you-go is billed hourly and can be released at any time — best for trials and short-term use. Subscription is pre-paid with lower overall costs — better for stable, long-term workloads. Serverless scales automatically — suited for unpredictable workloads.
    Region Singapore (or the region closest to your users) If connecting from an ECS instance, select the same region as the ECS instance for a faster internal network connection. The region cannot be changed after creation.
    Database Engine MySQL 8.0 Select MySQL 8.0 for new projects — it offers the latest features and performance improvements. For existing applications, match your application's MySQL version (5.6, 5.7, or 8.0 are supported).
    Edition High-availability Edition Provides redundancy and most key features at a cost-effective price. See Editions for a full comparison.
    Storage Type Premium ESSD Premium Local SSD or Premium ESSD both work for trials. Your choice affects which instance features are available. See Storage types for details.
    VPC Default If connecting from an ECS instance, select the same Virtual Private Cloud (VPC) as your ECS instance. Otherwise, keep the default.
    Instance Type mysql.n2.medium.2c Select an instance type suited to your workload. You can change the instance type after creation if needed.
    image
  3. Review your instance settings in the right-side panel. Hover over View Details to see a full cost breakdown. Once confirmed, click Confirm Order.

  4. After the Payment Complete page appears, click Console to return to the Instances page.

  5. Select your instance's region from the top navigation bar. Wait 1–10 minutes for the instance to finish creating — the status shows Creating during this time.

  6. When the status changes to Running, the instance is ready.

    If the instance doesn't appear immediately after creation, wait a moment and refresh the page.

Step 2: Create a database

  1. Go to the Instances page. Select the region of your instance from the top navigation bar, then click the instance ID.

    image
  2. In the left-side navigation pane, click Databases, then click Create Database.

    image
  3. In the Create Database panel, configure the following parameters:

    Parameter Suggested value Description
    Database Name db_test1 Enter a name for your database.
    Supported Character Set utf8 Use utf8 for most applications. Use utf8mb4 if you need to store 4-byte characters such as emojis.
    Authorized By (default) Keep the default value.
  4. Click Create.

  5. Go back to the Databases page to confirm the database appears in the list.

Step 3: Create a privileged account

  1. Go to the Instances page and click your instance ID. In the left-side navigation pane, click Accounts, then click Create Account.

    image
  2. In the Create Account panel, configure the following parameters:

    Parameter Suggested value Description
    Database Account dbuser Enter a name for the account.
    Account Type Privileged Account A privileged account has full management permissions on the instance. Use it to create standard accounts for fine-grained access control later.
    New Password Enter a password for the account.
    Confirm Password Confirm the password.
  3. Click OK.

  4. Go back to the Accounts page to confirm the privileged account appears in the list.

    RDS for MySQL supports two account types: Privileged and Standard. Use the privileged account to create standard accounts for more granular access control. For details, see Create an account.
    image

What's next

Step 2: Connect to an ApsaraDB RDS for MySQL instance

FAQ

Instance queries

How can I see all my RDS instances and their status?

Go to the Overview page of the RDS console. In the Resource Distribution section, you can see all running and total RDS instances across all regions in your account.

image

I just created an instance but it's not showing in the list. What's wrong?

The most common cause is an incorrect region selection — the instance is in a different region from the one you're viewing. Select the correct region from the top navigation bar.

If the instance still doesn't appear after switching regions, the creation may have failed due to insufficient resources in the selected zone. In that case, check the My Order page for a refund, then create a new instance in a different zone.

Accounts and permissions

How do I set up more fine-grained permissions for an account?

Use the privileged account you created in Step 3 to create standard accounts with specific database and table-level permissions. For details, see Authorize an account to access its authorized databases from specified IP addresses and Authorize accounts to manage tables, views, and fields.

Does RDS for MySQL provide a root user or SUPER privilege?

No. RDS for MySQL does not provide a root user or the SUPER privilege. This is by design: restricting these privileges prevents accidental misconfigurations that could cause data loss or service disruption, while the privileged account type gives you the management capabilities you need for day-to-day operations.

I got an error while creating an account. What should I check?

The error is most likely caused by one of the following:

  • A duplicate account name already exists on the instance

  • A privileged account already exists (only one is allowed per instance)

  • Too many account creation requests in a short period

Resolve the specific issue and try again.

References