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.

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 that you can subscribe to for a specified period of time and pay for up front. 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: A pay-as-you-go instance is charged per hour 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. If you no longer need the RDS instance, you can release the instance to reduce costs.
    Note
    • You can create a pay-as-you-go RDS instance. Then, after you confirm that the created RDS instance 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 the RDS instance is deployed, you must select Dedicated Cluster (Subscription) to create a host. Then, you can create the 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 the RDS instance runs. Select MySQL. Only MySQL 5.6, MySQL 5.7, and MySQL 8.0 are supported.
    Note The available database engines and versions vary based on the region that you select.
    Edition
    • Basic: 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.
    • High-availability: 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. These instances work in the high availability architecture. The RDS High-availability Edition is suitable for production environments.
    • Enterprise: In the RDS Enterprise Edition, the database system consists of a primary RDS instance, a secondary RDS instance, and a logger RDS instance. The RDS Enterprise Edition is suitable for financial institutions that have high requirements for reliability.
    Note
    Storage Type
    • Local SSD: A local SSD resides on the same host as the database engine. You can store data on local SSDs to reduce I/O latency.
    • ESSD: Enhanced SSDs (ESSDs) come in three performance levels (PLs).
      • ESSD PL1: An ESSD of PL1 is a regular ESSD.
      • 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.
    • Standard SSD: A standard SSD is an elastic block storage device that is built on top of the distributed storage architecture. You can store data on standard SSDs to separate computing from storage.
    Note
    • The available storage types vary based on the instance type and RDS edition that you select.
    • If you select the ESSD or standard SSD storage type, you can select the Disk Encryption option. Disk encryption improves data security. For more information, see Configure disk encryption for an ApsaraDB RDS for MySQL instance.
    • For more information about the storage types that are supported by ApsaraDB RDS, see Storage types.
    Zone of Primary Node

    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 storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files. You can adjust the storage capacity in increments of 5 GB.
    Note If you select the local SSD storage type, the storage capacity of the RDS instance may vary based on the instance type. If you select the standard SSD or ESSD storage type, the storage capacity of the RDS instance does not vary based on the instance type. For more information, see Primary ApsaraDB RDS instance types.
    Backup Retention After Release The policy based on which ApsaraDB RDS retains the backup data of the RDS instance after the RDS instance is released. If the RDS instance contains crucial data, we recommend that you select Latest or All. This way, you can retrieve the data if the data is lost due to overdue payments.
    Note This parameter is displayed only when you set the Billing Method parameter to Subscription.
  4. In the lower-right corner of the page, click Next: Instance Configuration.
  5. Specify the network type.
    Note If your application is deployed on an ECS instance, the ECS instance and the RDS instance must both reside in the classic network or reside in the same virtual private cloud (VPC). Otherwise, the ECS instance and the RDS instance cannot communicate over an internal network.
    • Classic Network: the traditional type of network.
    • VPC: the recommended type of network. A 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 also select a VPC and a vSwitch. If no VPCs or vSwitches are created within your Alibaba Cloud account, you can select the default VPC and vSwitch.

  6. 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 to how 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.
  7. In the lower-right corner of the page, click Next: Confirm Order.
  8. 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.
  9. View the RDS instance.
    Return to the ApsaraDB RDS homepage. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where the RDS instance resides. Then, find the RDS instance based on its Creation Time. ApsaraDB RDS requires approximately 10 minutes to create an RDS instance.

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?

    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