All Products
Search

This Product

    ApsaraDB for MyBase:Create a MySQL cluster

    Document Center

    ApsaraDB for MyBase:Create a MySQL cluster

    Last Updated:Jun 20, 2026

    You need to create an ApsaraDB for MyBase cluster before you can use the features in ApsaraDB for MyBase.

    Background information

    For more information about MyBase MySQL, see MyBase MySQL.

    Usage notes

    • An ApsaraDB for MyBase cluster can exist in only one region.

    • An ApsaraDB for MyBase cluster can belong to only one VPC.

    • You cannot set an oversubscription ratio when you Create Dedicated Cluster. You can modify the oversubscription ratio after the cluster is created. For details, see Set Cluster Oversubscription to Reduce Costs. The default oversubscription ratios for the MySQL engine are:

      • CPU Overcommit Ratio: 200%

      • Storage Overcommit Ratio: 100%

      • Maximum Memory Usage: 100%

    Procedure

    1. Log on to the ApsaraDB for MyBase console.

    2. In the upper-left corner of the page, select the region.

    3. On the Dedicated Clusters page, click Create Dedicated Cluster.

    4. On the Create Dedicated Cluster page, set the following parameters.

      Parameter

      Description

      Engine

      The database engine for the dedicated cluster. Select MySQL.

      Architecture

      The architecture of the dedicated cluster. The default value is High-availability Edition.

      Note

      Dedicated cluster name

      The name of the dedicated cluster.

      VPC

      The VPC to which the dedicated cluster belongs. To create a new VPC, go to the VPC console.

      Note

      You cannot change the VPC after the cluster is created. To change the VPC, you must delete the dedicated cluster and create a new one. Make sure that you select the correct VPC.

      Resource Allocation Policy

      The default policy that the dedicated cluster uses to schedule resources:

      • Balanced Allocation: Maximizes system stability. The system preferentially allocates resources from hosts with no allocated resources or fewer allocated resources.

      • Compact Allocation: Maximizes resource utilization. The system preferentially allocates resources from hosts that were created earlier and have more allocated resources.

      Host Troubleshooting Policy

      The policy for handling host failures:

      • Automatic Host Replacement: The system automatically replaces a faulty host.

        Note

        • If the faulty host uses an ESSD, the system automatically migrates its compute resources, replacing the host.

        • If the faulty host uses a local SSD, the system first migrates the instances on the host and then automatically replaces the host.

      • Manual Host Replacement: You must manually replace a faulty host.

      Grant OS Permissions

      Grants operating system (OS) permissions on the hosts of a dedicated cluster that runs the MySQL engine. You can then log on to the hosts to upload or download files, install software, and perform other operations.

      Note

      This setting cannot be changed after the cluster is created. Proceed with caution.

    5. This step is required only if you are creating a cluster for the first time.

      When you create an ApsaraDB for MyBase cluster for the first time, you are prompted to authorize access to ECS elastic network interfaces (ENIs) and security groups. Click Authorize Now. On the Cloud Resource Access Authorization page, click Confirm Authorization Policy.

      Note

      After you grant the authorization, you can find the AliyunRDSDedicatedHostGroupRole role on the Roles page of the Resource Access Management (RAM) console. Do not delete this role while using ApsaraDB for MyBase. If you delete this role, you must grant authorization again the next time you create a cluster.

    6. Click OK.