All Products
Search

This Product

    ApsaraDB RDS:Create a serverless ApsaraDB RDS for MySQL instance

    Document Center

    ApsaraDB RDS:Create a serverless ApsaraDB RDS for MySQL instance

    Last Updated:Aug 28, 2023

    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 RDS instance. For more information, see Use RAM for resource authorization.

    Procedure

    1. Go to the ApsaraDB RDS buy page.

    2. Set the Billing Method parameter 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 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, you cannot connect these instances over an internal network. In this case, these instances cannot deliver the optimal performance.

      Note

      • You can create serverless RDS instances only in the Singapore region.

      • After an RDS instance is created, you cannot change the region of the RDS instance. If you want to connect an ECS instance and 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 in which an ECS instance resides, 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 RDS instance to connect to the RDS instance from your application.

    4. Set the Database Engine parameter to MySQL 8.0 or MySQL 5.7.

    5. 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 RCUs.

    6. Optional. Click Advanced Settings to modify the Scaling Policy and Automatic Stop and Restart parameters based on your business requirements. For more information, see Configure a serverless ApsaraDB RDS for MySQL instance.

    7. Configure the Storage Type parameter. Only ESSD PL1 is supported.

      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.

      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.

    8. Select a zone for the RDS instance.

      Take note of the following items:

      • 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 deliver 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.

      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.

    9. If you want to create an RDS instance that runs RDS High-availability Edition, you must configure the Deployment Method and Zone of Secondary Node parameters. Valid values for the Deployment Method method are Multi-zone Deployment and Single-zone Deployment.

    10. You can drag the slider to change the storage capacity.

      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.

    11. In the lower-right corner of the page, click Next: Instance Configuration.

    12. Configure the VPC and VSwitch of Primary Node parameters. We recommend that you select the same virtual private cloud (VPC) in which your ECS instance resides. If the RDS instance and the ECS instance reside in different VPCs, you cannot connect these instances 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 RDS instance and the ECS instance over an internal network even if the instances use different vSwitches in the same VPC.

    13. 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 set this parameter to Yes, 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 retain the default values of these parameters.

      Parameter

      Description

      Parameter Template

      Select 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 Zone

      Select a time zone for the RDS instance.

      Table Name Case Sensitivity

      By default, this parameter is set to Case-insensitive. If the names of on-premises databases are case-sensitive, we recommend that you select Case-sensitive to facilitate data migration.

      Release Protection

      Select this option to prevent the RDS instance from being accidentally deleted. For more information, see Enable or disable the release protection feature for an ApsaraDB RDS for MySQL instance.

      Resource Group

      Use the default resource group or select a custom resource group based on your business requirements. This facilitates instance management.

      Privileged Account

      If 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.

    16. Confirm the configuration of and configure the Purchase Plan parameter. Then, read and select Terms of Service, click Pay Now, and then complete the payment.

      The Congratulations. or The service is activated message is displayed in the ApsaraDB RDS console.

    17. View the RDS instance.

      Go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides. Then, find the RDS instance based on the Creation Time parameter.

      It requires 1 to 10 minutes to create a serverless RDS instance. You can refresh the page to view the new RDS instance.

    What to do next

    Create databases and accounts for an ApsaraDB RDS for MySQL instance

    FAQ

    • After I submit the order for purchasing an RDS instance, why am I unable to find the RDS instance in the Creating state on the Instances page?

      Cause

      Description

      Suggestion

      Incorrect region

      The 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 resources

      The 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.

    • What is the maximum number of connections that can be established to a serverless RDS instance? Can I change the maximum number of connections that can be established to a serverless RDS instance?

      The maximum number of connections that can be established to a serverless RDS instance is 10,000. You cannot modify the maximum number of connections that can be established to a serverless RDS instance.

    What to do next