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

Prerequisites

The AliyunRDSFullAccess policy is attached to the RAM user that you use to create the RDS instance. For more information, see Use RAM for resource authorization.

Procedure

  1. Go to the ApsaraDB RDS buy page.
  2. Configure the Billing Method parameter.
    Billing methodDescriptionBenefit
    SubscriptionA subscription instance is an instance for which you pay an upfront fee. If you want to use an instance for a long period of time, we recommend that you select the Subscription billing method. If you select the subscription billing method, configure the Duration parameter in the lower part of the page. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription periods.
    Pay-as-you-goYou are charged on an hourly basis for a pay-as-you-go instance based on your actual resource usage. If you want to use an 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 RDS instance meets your business requirements, you can change the billing method of the RDS instance from pay-as-you-go 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.
    ServerlessIf you want to run scheduled tasks, your business workloads frequently change, or the business workloads are fully managed or do not require O&M, we recommend that you select Serverless.
    Note
    If you select serverless, you are charged based on your consumption of resources for workloads. This can help reduce costs.
    Note You can view the price in the lower-right corner of the page. The price is displayed only after you configure all required parameters.
  3. Configure the Region parameter.
    We recommend that you create the RDS instance in the same region as the Elastic Compute Service (ECS) instance on which your application is deployed. If the RDS instance and the ECS instance reside in different regions, these instances cannot communicate over an internal network. As a result, these instances cannot deliver optimal performance.
    Note
    • After an RDS instance is created, you cannot change the region of the RDS instance. If an ECS instance connects to an RDS instance over an internal network, make sure that the RDS instance and the ECS instance reside in the same region.
    • For more information about how to view the region where an ECS instance resides, see Get ready to use ApsaraDB RDS for MySQL.
    • If your application is deployed on an on-premises server or on-premises computer, we recommend that you select a region that is near your on-premises server or on-premises computer. This way, you can use the public endpoint of the RDS instance to connect to the RDS instance from your application.
  4. Configure the Database Engine parameter.
    In this example, MySQL is selected.

    We recommend that you select MySQL 8.0 or MySQL 5.7 or select the database engine version that your self-managed MySQL instance runs. The default value of this parameter is MySQL 8.0.

    Note Serverless RDS instances support MySQL 5.7 and MySQL 8.0.
  5. Configure the Edition parameter. The default value of this parameter is High-availability.
    RDS editionDescriptionBenefit
    BasicIn RDS Basic Edition, the database system consists of only a primary RDS instance. 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 EditionThis is the recommended RDS edition. In 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. You can create read-only RDS instances and attach the read-only RDS instances to the primary RDS instance. RDS High-availability Edition is suitable for more than 80% of business scenarios that require production environments.
    EnterpriseIn RDS Enterprise Edition, the database system consists of a primary RDS instance, a secondary RDS instance, and a logger RDS instance. You can create read-only RDS instances and attach the read-only RDS instances to the primary RDS instance. 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 Basic option is not displayed.
    • Serverless RDS instances run only RDS Basic Edition.
    • For more information, see Overview of ApsaraDB RDS editions.
  6. Configure the Architecture parameter. Only x86 is supported.
  7. Configure the Storage Type parameter.
    Comparison itemESSD (Recommended)Local SSD
    Scalability★★★★★
    • You can increase the storage capacity up to 32 TB.
    • No transient connections occur during storage expansion.
    • You can upgrade, downgrade, create, or release the RDS instance in minutes.
    • Automatic storage expansion is supported.
    ★★
    • You can increase the storage capacity up to 6 TB.
    • Transient connections occur during storage expansion.
    • A few hours may be required to upgrade, downgrade, create, or release the RDS instance.
    • Automatic storage expansion is not supported.
    Performance★★★★★
    • PL1<PL2<PL3
    • An enhanced SSD (ESSD) of performance level 2 (PL2) provides twice the IOPS and throughput of an ESSD of performance level 1 (PL1).
    • An ESSD of PL3 provides 20 times the IOPS and 11 times the throughput of an ESSD of PL1.
    Note ApsaraDB RDS provides three storage types. For more information, see Storage types.
    ★★★★★
    Backup★★★★★
    • A backup can be completed in minutes or seconds.
    • The highest backup frequency is one backup every 15 minutes.
    ★★★
    • A backup requires a long period of time.
    • The highest backup frequency is one backup every day.
    Note
    • RDS instances that run MySQL 5.7 or MySQL 8.0 on RDS Basic Edition support only standard SSDs and ESSDs. RDS instances that run MySQL 5.7 or MySQL 8.0 on RDS Enterprise Edition support only local SSDs. RDS instances that run MySQL 5.5 or MySQL 5.6 on RDS High-availability Edition support only local SSDs. Serverless RDS instances support only standard SSDs and ESSDs.
    • The available features vary based on the storage type that you select. For more information, see MySQL 8.0.
  8. Select the zone in which the RDS instance resides.
    • Select a zone.
      • No significant differences exist between the zones in the same region.
      • If the RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can provide the optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.
    • Select a deployment method.
      • Multi-zone Deployment: This is the recommended deployment method. The primary RDS instance and the secondary RDS instance reside in different zones to provide zone-disaster recovery.
      • Single-zone Deployment: The RDS instance and the secondary RDS instance reside in the same zone.
      Note f you select Basic for the Edition parameter, only the Single-zone Deployment method is supported.
  9. Configure the Instance Type parameter.
    1. Configure the Category parameter. You can select General-purpose or Dedicated.
      CategoryDescriptionBenefit
      General-purposeA general-purpose RDS instance exclusively occupies the allocated memory and I/O resources.

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

      General-purpose RDS instances are cost-effective.
      DedicatedA dedicated RDS 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 RDS instance exclusively occupies all the CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.
      A dedicated RDS instance can provide higher performance and higher stability.
      Note An RDS instance that runs RDS Basic Edition does not support the dedicated instance family.
    2. Configure detailed specifications, including cores and memory capacity.
      • In a test environment, select an instance type that provides one or more cores.
      • In a production environment, select an instance type that provides four or more cores.
      Note For more information about instance types, see Primary ApsaraDB RDS for MySQL instance types (x86).
      Select an instance type
  10. Configure the Capacity parameter.

    The valid values of the Capacity parameter vary based on the instance type and storage type that you select.

    You can adjust the storage capacity at a step size of 5 GB.
  11. Configure the following parameters. This step is required only when you select the Subscription billing method and the Local SSD storage type.
    We recommend that you set the Backup Retention After Release parameter to Latest or All. This way, you can retrieve the data of the RDS instance if the RDS instance is released due to overdue payments and data is lost. Backup Retention After Release
  12. In the lower-right corner of the page, click Next: Instance Configuration.
    Next: Instance Configuration
  13. Configure the Network Type parameter.
    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. For more information, see Get ready to use ApsaraDB RDS for MySQL.
      • If the ECS instance does not need to communicate with the RDS instance over an internal network, you can select the classic network type or the VPC network type.
      • Some RDS instances do not support the classic network type.
    2. VPC and VSwitch of Primary Node: 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 on which your application is deployed. If the RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.
    3. Add to Whitelist: If you set the Network Type parameter to VPC, you must specify whether to add the CIDR block of the selected VPC to the whitelist of the RDS instance. If you select Yes for the Add to Whitelist parameter, the ECS instances that reside in the selected VPC can access the RDS instance.
  14. Configure other custom parameters. If you do not have special business requirements, you can use the default values of these parameters.
    ParameterDescription
    Release ProtectionSpecifies whether to enable the release protection feature. The release protection feature is used to prevent a pay-as-you-go RDS instance from being released due to unintended operations. For more information, see Enable or disable the release protection feature for an ApsaraDB RDS for MySQL instance.
    Minor Version Upgrade PolicyThe policy based on which the minor engine version of the RDS instance is updated.
    • Automatic Upgrade: ApsaraDB RDS automatically updates the minor engine version of the RDS instance to the most recent version during the maintenance window. 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 update time, see Manage scheduled 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 is displayed.

    Resource GroupThe 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.
    Privileged AccountIf you select Now, you must configure the Database Account, Password, and Confirm Password parameters to create a privileged account. If you select Later, you can create a privileged account after the RDS instance is created.

    For more information about privileged accounts, see Create a privileged account.

  15. In the lower-right corner of the page, click Next: Confirm Order.
    Next: Confirm Order
  16. Confirm the configuration of the RDS instance in the Parameters section, configure the Purchase Plan and Duration parameters, read and select Terms of Service, and then click Pay Now. You must configure 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 way, you can prevent interruptions on your application even if you forget to renew the RDS instance.
    The Congratulations. or The service is activated message is displayed in the ApsaraDB RDS console.
  17. View your serverless RDS instance.
    Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance based on the Creation Time parameter.

    ApsaraDB RDS requires 1 to 10 minutes to create an RDS instance. You can refresh the page to view the RDS instance that you created.

    Creating

What to do next

Create databases and accounts 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 causeAnomaly descriptionSuggestion
Incorrect regionThe 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 resourcesThe 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 instancesRAM 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 SSDs, the RDS instance cannot be created. When you create an RDS instance that uses local SSDs, you cannot enable disk encryption.
  • If you use the credentials of the RAM user to create an RDS instance that uses standard SSDs or ESSDs and you do not enable 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 Disk Encryption, configure the Key parameter, and then try again.

References