This topic describes how to create an ApsaraDB RDS for MySQL instance.

Note You receive a discount on your first purchase of an RDS instance. For more information, visit the ApsaraDB RDS promotion page.

Procedure

  1. Go to the ApsaraDB RDS buy page.
  2. Specify the Billing Method parameter.
    Billing method Description Benefit
    Subscription A subscription instance is an instance for which you pay an upfront fee. If you plan to use the RDS instance for a long period of time, we recommend that you select the Subscription billing method. In this case, you also need to 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 can receive larger discounts for longer commitments.
    Pay-As-You-Go You are charged an hourly fee for a pay-as-you-go instance based on your actual resource usage. If you plan to use the RDS instance for a short period of time, we recommend that you select the Pay-As-You-Go billing method.

    You can create a pay-as-you-go RDS instance. After you confirm that the created RDS instance meets your business requirements, you can change the billing method of the RDS instance to subscription.

    You can release a pay-as-you-go RDS instance at any time. The billing of a pay-as-you-go RDS instance stops immediately after you release the instance.
    Note
    • You can view the price in the lower-right corner of the page. The price appears only after you configure all the required parameters.
    • If you select the subscription or pay-as-you-go billing method, you can manage the RDS instance but cannot manage the host on which the RDS instance is deployed. If you want to manage the host on which the RDS instance is deployed, you must select Dedicated Cluster (Subscription). For more information, see Quick start.
  3. Specify the Region parameter.
    We recommend that the RDS instance reside in the same region as the Elastic Compute Service (ECS) instance that you want to connect. 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.
    Note 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. Then you can connect to the RDS instance from your application by using the public endpoint of the instance.
  4. Specify the Database Engine parameter.
    Select MySQL.

    We recommend that you select MySQL 8.0 or MySQL 5.7 or select the database engine version that is run on your self-managed MySQL instance. The default MySQL version is 8.0.

  5. Specify the Edition parameter. The default value is High-availability Edition.
    Edition Description Benefit
    Basic Edition In the RDS Basic Edition, the database system consists of only a primary RDS instance. The RDS Basic Edition is cost-effective and is suitable for learning and testing.

    RDS instances that run the RDS Basic Edition require a long period of time to restart or recover from faults.

    High-availability Edition This is the recommended edition. In the RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance. The primary RDS instance can be attached with read-only RDS instances. The RDS High-availability Edition is suitable for more than 80% of production environments.
    Enterprise Edition In the RDS Enterprise Edition, the database system consists of a primary RDS instance, a secondary RDS instance, and a logger RDS instance. The primary RDS instance can be attached with read-only RDS instances. The RDS Enterprise Edition is suitable for financial institutions that have high requirements for reliability.
    Note
    • The available RDS editions vary based on the region and database engine version that you select. If you select MySQL 5.6, the RDS Basic Edition is not displayed.
    • For more information, see Overview of ApsaraDB RDS editions.
  6. Specify the Storage Type parameter.
    Item ESSD (Recommended) Local SSD
    Scalability ★★★★★
    • Up to 32 TB.
    • No transient connection occurs during a storage expansion operation.
    • You can upgrade, downgrade, create, or release the RDS instance in minutes.
    • Automatic storage expansion is supported.
    ★★
    • Up to 6 TB.
    • Transient connection occurs during a storage expansion operation.
    • You may require a few hours to upgrade, downgrade, create, or release the RDS instance.
    • Automatic storage expansion is not supported.
    Performance ★★★★★
    • ESSD of PL1 < ESSD of PL2 < ESSD of PL3
    • An ESSD of PL2 delivers IOPS and throughput that are twice higher than the IOPS and throughput delivered by an ESSD of PL1.
    • An ESSD of PL3 delivers IOPS that is 20 times higher than the IOPS delivered by an ESSD of PL1. An ESSD of PL3 also delivers throughput that is 11 times higher than the throughput delivered by an ESSD of PL1.
    ★★★★★
    Backups ★★★★★
    • Backups can be completed in minutes or seconds.
    • The highest backup frequency is one backup every 15 minutes.
    ★★★
    • Backups require a long period of time.
    • The highest backup frequency is one backup every week.
    Note
    • Standard SSDs are being phased out.
    • RDS instances that run MySQL 5.7 or MySQL 8.0 on RDS Basic Edition support only ESSDs. RDS instances that run MySQL 8.0 or MySQL 5.7 on RDS Enterprise Edition support only local SSDs. RDS instances that run MySQL 5.6 or MySQL 5.5 on RDS High-availability Edition support only local SSDs.
    • The available features vary based on the storage type that you select. For more information, see Features of ApsaraDB RDS for MySQL.
    • For more information about the supported storage types, see Storage types.
  7. Select the zone where the RDS instance resides.
    • Select a zone.
      • No substantive differences exist between zones in the same region.
      • If the RDS instance resides in the same region as the ECS instance that you want to connect, these instances can deliver optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of these instances slightly decreases.
    • Select a deployment method.
      • Multi-zone Deployment: The RDS instance and its secondary RDS instance reside in different zones to provide zone-disaster recovery. This is the recommended deployment method.
      • Single-zone Deployment: The RDS instance and its 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.
  8. Specify the Instance Type parameter.
    1. Before you select an instance type, you must select an instance family.
      Instance family Description Benefit
      General-purpose A general-purpose instance exclusively occupies the allocated memory and I/O resources.

      A general-purpose instance shares CPU and storage resources with the other general-purpose instances that are deployed on the same host.

      General-purpose instances are cost-effective.
      Dedicated A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources.
      Note The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources of the host on which the instance is deployed.
      A dedicated instance can provide better performance and stability.
      Note An RDS instance that runs the RDS Basic Edition does not support the dedicated instance family.
    2. Select an instance type.
      • For test purposes: 1 core or more.
      • For production purposes: 4 cores or more.
      Note For more information, see Primary ApsaraDB RDS for MySQL instance types.
      Select specifications
  9. Specify the Capacity parameter.

    The value range of the storage capacity varies based on the instance type and storage type that you select.

    You can adjust the storage capacity at a step size of 5 GB.
  10. Configure the following parameters. You need to perform this step only when you select the Subscription billing method and the Local SSD storage type.
    Backup Retention After Release: We recommend that you select Latest or All. This way, you can retrieve the data of the RDS instance if the data is lost due to overdue payments. Backup Retention After Release
  11. In the lower-right corner of the page, click Next: Instance Configuration.
    Instance Configuration
  12. Specify the network configuration.
    1. Network Type: If your application is deployed on an ECS instance, the ECS instance and the RDS instance must have the same network type. Otherwise, the ECS instance and the RDS instance cannot communicate over an internal network.
      Note
      • You must check the network type of your ECS instance before you create an RDS instance.
      • If the ECS instance on which your application is deployed does not need to connect to the RDS instance over an internal network, you can select the classic or VPC network type.
      • Some RDS instances do not support the classic network.
    2. VPC and vSwitch: If you select the VPC network type, you must also select a VPC and a vSwitch. We recommend that you select the VPC of the ECS instance that you want to connect. If the RDS instance and the ECS instance reside in different VPCs, the ECS instance and the RDS instance cannot communicate over an internal network.
      Note
      • You must check the VPC of the ECS instance before you create an RDS instance.
      • If the RDS instance and the ECS instance belong to different vSwitches within the same VPC, these instances can also communicate over an internal network.
  13. Configure custom parameters. If you do not have special business requirements, you can retain the default values of these parameters.
    Parameter Description
    Minor Version Upgrade Policy The policy that is used to update the minor engine version of the RDS instance.
    • Automatic Upgrade: ApsaraDB RDS automatically updates the minor engine version of the RDS instance to the latest version within the maintenance window that you specify. For more information about how to change the maintenance window, see Set the maintenance window of an ApsaraDB RDS for MySQL instance. For more information about how to change the upgrade time, see Manage pending events.
    • Manual Upgrade: You must manually update the minor engine version of the RDS instance on the Basic Information page.

    If you do not want to use the latest minor engine version, select Select Minor Version. Then, you can select a minor engine version from the drop-down list that appears.

    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.
  14. In the lower-right corner of the page, click Next: Confirm Order.
    Next: Confirming Order
  15. 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.
    The "Congratulations." or "The service is activated" message is displayed in the ApsaraDB RDS console.
  16. View the RDS instance.
    Open 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. Then, refresh the page.

    Creating

What to do next

Create accounts and databases for an ApsaraDB RDS for MySQL instance

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?
Possible cause Description Solution
Different Region 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.
Insufficient resources The zone that you selected cannot provide sufficient resources.

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

We recommend that you select a different zone and try again.

References