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

Prerequisites

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

Procedure

  1. Go to the ApsaraDB RDS buy page.
  2. Set Billing Method to Serverless.
    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 serverless RDS instance in the same region as the Elastic Compute Service (ECS) instance on which your application is deployed. If the serverless RDS instance and the ECS instance reside in different regions, you cannot connect these instances over an internal network. In this case, these instances cannot deliver the optimal performance.
    Note
    • After a serverless RDS instance is created, you cannot change the region of the serverless RDS instance. If you want to connect an ECS instance and a serverless RDS instance over an internal network, make sure that the serverless RDS instance and the ECS instance reside in the same region.
    • For more information about how to view the region of an ECS instance, see Get ready to use ApsaraDB RDS for MySQL.
    • If your application is deployed on an on-premises server or computer, we recommend that you select a region that is near your on-premises server or computer. This way, you can use the public endpoint of the serverless RDS instance to connect to the serverless RDS instance from your application.
  4. Configure the Minimum and Maximum parameters for RDS Capacity Units (RCUs). This way, your serverless RDS instance can be automatically scaled by measuring the usage of RCUs.
    Note A serverless RDS instance is billed based on RDS Capacity Units (RCUs).
  5. Optional:Click Advanced Settings to adjust the configurations of scaling policy and automatic start and stop feature based on your business requirements. For more information, see Configure a serverless ApsaraDB RDS for MySQL instance.
  6. Select a value for Storage Type. Only ESSD PL1 can be selected.
    An enhanced SSD (ESSD) is an ultra-high performance disk that is designed by Alibaba Cloud based on the next-generation distributed block storage architecture. ESSDs use 25 Gigabit Ethernet and RDMA technologies to deliver up to 1 million random read/write IOPS per disk and reduce one-way latency. ESSDs are provided in the following performance levels (PLs):
    • ESSD PL1: This refers to ESSDs of PL1.
    • ESSD PL2: An ESSD of PL2 delivers IOPS and throughput that are about two times higher than the IOPS and throughput that are delivered by an ESSD of PL1.
    • ESSD PL3: An ESSD of PL3 delivers IOPS that is up to 20 times higher than the IOPS that is delivered by an ESSD of PL1. An ESSD of PL3 also delivers throughput that is up to 11 times higher than the throughput that is 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.
    Note
    • The storage capacity of your serverless RDS instance is automatically expanded based on your business requirements.
    • For more information about storage types of an RDS instance, see Storage types.
  7. Select the zone in which the RDS instance resides.in which the serverless RDS instance resides.
    Take note of the following items:
    • No significant differences exist between the zones in the same region.
    • If the serverless RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can deliver optimal performance. If the serverless RDS instance and the ECS instance reside in different zones in the same region, the performance of the serverless RDS instance and the ECS instance is slightly lower than the performance of the serverless RDS instance and the ECS instance that reside in the same zone.
    Note If Sold Out appears in the upper-right corner of a zone name, this zone does not have sufficient resources. In this case, change the zone.
  8. Configure the Capacity parameter.
    Note The value of the Capacity parameter specifies the minimum storage capacity of the serverless RDS instance. The serverless RDS instance automatically scales out the storage capacity based on your actual usage. After the storage capacity is scaled out, you cannot scale in the storage capacity and you are charged based on the new storage capacity.
  9. In the lower-right corner of the page, click Next: Instance Configuration.
  10. Select values for VPC and VSwitch of Primary Node. We recommend that you select the same virtual private cloud (VPC) in which your ECS instance resides. If the serverless RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.
    Note
    • For more information about how to view the VPC in which your ECS instance resides, see Get ready to use ApsaraDB RDS for MySQL.
    • You can connect the serverless RDS instance and the ECS instance over an internal network even if the instances reside in the same VPC and use different vSwitches.
  11. Configure the Add to Whitelist parameter to 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.
  12. Configure other custom parameters. If you do not have special business requirements, you can use the default values of these parameters.
    ParameterDescription
    Parameter TemplateSelect a high-performance parameter template, synchronous parameter template, or default parameter template. Parameters in the template that you select are displayed on the right. For more information, see Use a parameter template to configure the parameters of ApsaraDB RDS for MySQL instances.
    Time ZoneSelect a time zone for your serverless RDS instance.
    Table Name Case SensitivityBy default, this parameter is set to Case-insensitive. If the databases in your serverless RDS instance have case-sensitive names, we recommend that you select Case-sensitive.
    Release ProtectionSelect this option to prevent your serverless RDS instance from being deleted by mistake. For more information, see Enable or disable the release protection feature for an ApsaraDB RDS for MySQL instance.
    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.

  13. In the lower-right corner of the page, click Next: Confirm Order.
  14. Confirm the configuration of the serverless RDS instance, and configure Purchase Plan. Then, select Terms of Service, click Pay Now, and complete the payment.
    The Congratulations. or The service is activated message is displayed in the ApsaraDB RDS console.
  15. View your serverless RDS instance.
    Go to the Instances page. In the top navigation bar, select the region in which your serverless RDS instance resides. Then, find the serverless RDS instance based on the Creation Time parameter.

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

What to do next

Create databases and accounts for an ApsaraDB RDS for MySQL instance

FAQ

Why am I unable to find the RDS instance that I created?
Possible causesAnomaly 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.

References