ApsaraDB RDS:Create an ApsaraDB RDS for MySQL instance

New version of the ApsaraDB RDS buy page

1. Open the ApsaraDB RDS buy page of the new version.

2. Configure the Billing Method parameter.

   Billing Method	Recommendation	Benefit
   Subscription	For long-term use, select Subscription (pay in advance) and configure the Subscription Duration parameter in the lower-left corner of the page.	The subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription durations.
   Pay-As-You-Go	For short-term use, select Pay-As-You-Go (billed by hour). You can create a pay-as-you-go RDS instance and switch the billing method of the RDS instance to subscription after you confirm that the RDS instance meets your requirements.	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.
   Serverless	If you need to process scheduled tasks, handle fluctuating workloads, use fully managed services, or eliminate the need for O&M, select Serverless. Note For more information about serverless RDS instances and how to create serverless RDS instances, see Serverless ApsaraDB RDS for MySQL.	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 select the region in which your ECS instance resides for the RDS instance. If the RDS instance and the ECS instance reside in different regions, these instances cannot communicate over an internal network. In this case, these instances cannot deliver optimal performance.

   Note

   • 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 of your ECS instance, see Preparations.

   • 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. Configure the Database Engine, Edition, Product Type, and Storage Type parameters.

   1. Configure the Database Engine parameter.

      This topic describes how to create an ApsaraDB RDS for MySQL instance. Select MySQL. We recommend that you select MySQL 8.0 or select the database engine version that is run on your self-managed MySQL instance. The default MySQL version is 8.0.

      Note

      • Serverless RDS instances support MySQL 5.7 and MySQL 8.0.

      • For more information about the lifecycle of MySQL major versions, see Lifecycle of MySQL major versions.

   2. Configure the Edition parameter.

      Edition	Description	Feature
      Basic Edition	A node.	RDS Basic Edition is cost-effective and is suitable for learning and testing. RDS instances that run RDS Basic Edition require a long period of time to restart or recover from faults.
      High-availability Edition	In RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance. 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 in production environments.
      Cluster Edition (Recommended)	In RDS Cluster Edition, the database system consists of a primary node and multiple secondary nodes.	In RDS Cluster Edition, primary and secondary nodes work in HA mode and the secondary nodes are readable.

      Note

      • The available RDS editions vary based on the region and database engine version that you select.

      • RDS Cluster Edition supports MySQL 8.0 and MySQL 5.7.

      • For more information about RDS editions, see Overview of ApsaraDB RDS editions.

   3. Configure the Product Type parameter.

      You can select Standard or YiTian. For more information, see Product types.

      Note

      • YiTian RDS instances support MySQL 8.0 and MySQL 5.7.

      • If your RDS instance runs RDS Basic Edition, you do not need to configure this parameter.

   4. Configure the Storage Type parameter.

      Comparison item	Enhanced SSD	Premium Performance Disk (Recommended)	Local SSD
      Elastic Scalability	★★★★★ Maximum storage capacity: 64,000 GB. No transient connections occur during storage expansion. You can upgrade, downgrade, create, or release the RDS instance within minutes. Automatic storage expansion is supported.	★★★★★ If your RDS instance runs MySQL or PostgreSQL, online storage capacity expansion is supported, and you can expand the storage capacity of your RDS instance within a few seconds.	★★ Maximum storage capacity: 8,000 GB. Transient connections occur during storage expansion. The upgrade, downgrade, creation, or release of an RDS instance may require several hours. The automatic storage expansion feature is not supported.
      Performance	★★★★★ PL1<PL2<PL3 An enhanced SSD (ESSD) of performance level 2 (PL2) delivers twice the IOPS and throughput of an ESSD of PL1. An ESSD of PL3 delivers IOPS that is up to 20 times the IOPS delivered by an ESSD of PL1. An ESSD of PL3 also delivers throughput that is up to 11 times the throughput delivered by an ESSD of PL1. Note ApsaraDB RDS provides three storage types. For more information, see Storage types.	★★★★★★ Premium performance disks are compatible with all features of ESSDs. Premium performance disks provide higher baseline I/O performance than PL1 ESSDs. Premium performance disks also provide the I/O burst, Buffer Pool Extension (BPE), and data archiving features. For more information, see What are premium performance disks? and Improvement in baseline I/O performance of premium performance disks for ApsaraDB RDS.	★★★★★ Reduces I/O latencies and improves I/O performance.
      Backup	★★★★★ A backup can be completed within minutes or seconds. The highest backup frequency is one backup every 15 minutes.	★★★★★ A backup can be completed within minutes or seconds. The highest backup frequency is one backup every 15 minutes.	★★★ A backup requires a long period of time to complete. The highest backup frequency is one backup every day.

      Note

      • If your RDS instance runs MySQL 8.0 or MySQL 5.7 and RDS Basic Edition, the RDS instance supports only cloud disks. If your RDS instance runs MySQL 5.6 or MySQL 5.5 and RDS High-availability Edition, the RDS instance supports only local SSDs. Serverless RDS instances support only cloud disks.

      • For more information about the differences between cloud disks and local SSDs, see Features of ApsaraDB RDS for MySQL.

   5. (Optional) If you select a cloud disk for your RDS instance, you can enable disk encryption.

5. Configure the network of the RDS instance. The Network Type parameter is set to VPC by default.

   1. Configure the VPC parameter.

      Note

      We recommend that you select the virtual private cloud (VPC) in which your ECS instance resides for the RDS instance. If the RDS instance and the ECS instance reside in different VPCs, these instances cannot communicate over an internal network.

   2. Specify whether to Add VPC CIDR Block To Whitelist.

      Note

      If you set this parameter to No, you can manually configure a whitelist after the RDS instance is created. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for MySQL instance.

6. Configure the zone, vSwitch, network, and deployment method of the RDS instance.

   • Select a zone

     A zone is an independent physical location within a region. For example, the China (Hangzhou) region contains Zone H, Zone I, and Zone J.

     • No substantive 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.

   • Select a vSwitch

     A vSwitch is a basic network device that connects different cloud resources. When you create a cloud resource in a VPC, you must specify a vSwitch to which the cloud resource is connected.

     You can select an existing vSwitch or click Create VSwitch to create a vSwitch. For more information about how to configure the parameters, see Create and manage a vSwitch.

   • Select a deployment method

     • Multi-zone Deployment (recommended): The primary node and secondary node are deployed in different zones in the same region. This deployment method provides cross-zone disaster recovery.

       If you select Multi-zone Deployment, you must configure the Primary Zone And Network and Secondary Zone And Network parameters.

     • Single-zone Deployment: The primary node and secondary node are deployed in the same zone.

       If you set the Edition parameter to Basic Edition, you can select only Single-zone Deployment.

     Note

     • For an RDS instance that consists of primary and secondary nodes, we recommend that you select Multi-zone Deployment to implement cross-zone disaster recovery.

     • If you set the Edition parameter to Cluster Edition, you must also specify the number of secondary nodes and the zones in which the primary and secondary nodes are deployed.

7. Configure the Instance Type parameter.

   1. Configure the Type parameter (General-purpose or Dedicated).

      Type	Description	Feature
      General-purpose	A general-purpose RDS instance exclusively occupies the allocated memory and I/O resources. A general-purpose RDS instance shares CPU and storage resources with other general-purpose RDS instances that are deployed on the same host.	General-purpose RDS instances are cost-effective.
      Dedicated	A dedicated RDS instance occupies all 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 occupies all CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.	A dedicated RDS instance delivers 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 CPU cores and memory capacity. For more information about instance types, see Primary instance types of ApsaraDB RDS for MySQL.

      • In a test environment, select an instance type that provides one or more cores.

      • In a production environment, we recommend that you select an instance type that provides four or more cores.

      Note

      If you set the Edition parameter to Cluster Edition, the Pricing column displays the price per node in the cluster. If you purchase one primary node and two secondary nodes for the cluster, the price of the cluster is triple the price that is displayed in the Pricing column.

8. Configure the Database Proxy parameter.

   The general-purpose database proxy feature is provided free of charge and can be enabled on the ApsaraDB RDS buy page or after an ApsaraDB RDS instance is created. The feature supports advanced capabilities such as read/write splitting, persistent connections, transaction splitting, connection pooling, and SSL encryption. The system enables the database proxy feature based on the recommended specifications. For more information, see Recommended specifications.

   Note

   • When you create an RDS instance that runs RDS High-availability Edition, the database proxy feature is disabled for the RDS instance. You can enable the general-purpose database proxy feature for the RDS instance.

   • When you create an RDS instance that runs RDS Cluster Edition, the general-purpose database proxy feature is enabled for the RDS instance. You can manually disable the feature.

   • If you want to change the specifications or type of the database proxy, you can modify the database proxy configurations after the RDS instance is created. For more information, see Modify the settings of the database proxy.

9. Configure the Storage Capacity parameter.

   The valid values of the Storage 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.

   Note

   If you select RDS High-availability Edition and a cloud disk, you can select Enable Automatic Storage Expansion and configure the trigger condition and upper limit for automatic storage expansion. If automatic storage expansion is triggered, ApsaraDB RDS automatically increases the storage capacity based on the larger value between 5 GB and 15% of the current storage capacity. This helps prevent the RDS instance from being locked due to insufficient storage resources.

10. (Optional) If you select Subscription and Local SSD, you must configure the Backup Retention Policy After Release parameter. We recommend that you select Retain Last Backup or Retain All Backups to prevent data loss due to unintended subscription expiration. For more information, see Long-term backup retention.

11. (Optional) If you set the Billing Method parameter to Subscription, you must configure the Subscription Duration parameter. You can refer to the following descriptions to configure this parameter.

    • Base Price: the original price of a subscription RDS instance without discounts.

    • Monthly Cost: the monthly cost of a subscription RDS instance that is calculated based on the base price.

    • Configuration Fee: You can move the pointer over View Details in the right side of the page to view the estimated total fee and fee details that are calculated based on the selected subscription duration and the base price of the RDS instance.

12. (Optional) Configure custom parameters. If you do not have special requirements, you can retain the default values.

    Parameter	Description
    Port	You can initialize the port when you create an RDS instance. Valid values: 1000 to 65534.
    Default Storage Engine	InnoDB: an open source default storage engine that can provide comprehensive features. This is the recommended storage engine. X-Engine: a storage engine that is developed by Alibaba. X-Engine is compatible with InnoDB and provides a high compression ratio. X-Engine can save more than 60% of storage space. Note This parameter is available only when you select MySQL 8.0 and High-availability or Basic Edition in the previous step.
    Parameter Template	Select the high-performance, asynchronous, default, or custom parameter template based on your business requirements. The parameters in the parameter template are displayed on the right. For more information, see Use a parameter template. Note This parameter is available only when you select High-availability or Basic Edition in the previous step.
    Time Zone	Select a time zone for your RDS instance. Note This parameter is available only when you select High-availability or Basic Edition in the previous step.
    Table Name Case Sensitivity	The default value is Case-insensitive. If your self-managed database is case-sensitive to table names, you can set this parameter to Case-sensitive to facilitate data migration. Note This parameter is available only when you select High-availability or Basic Edition in the previous step.
    Release Protection	Specifies 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 instance.
    Minor Version Upgrade Policy	Configure a policy based on which the minor engine version of the RDS instance is updated: Auto Upgrade (recommended): The system automatically upgrades the minor engine version of the RDS instance to the latest version during the maintenance window. You can modify the upgrade time on the Scheduled Events page. Manual Upgrade: You can manually upgrade the minor engine version of the RDS instance on the Basic Information page of the RDS instance. Note If you do not want to use the latest minor engine version, you can select Select Minor Version to specify a minor engine version.
    Resource Group	You can use the default resource group or select a custom resource group based on your business requirements. This facilitates instance management.
    Instance Description	Enter a description for easy identification.
    Tags	If you have many instances, you can attach tags to the instances to categorize and manage them. For more information, see Filter instances by tag.
    Privileged Account	You can select Set Now to create a privileged account by specifying an account name and a password. You can also click Set Later to create a privileged account after the RDS instance is created. For more information about privileged accounts, see Create a privileged account.

13. In the upper-right corner of the page, configure the Quantity parameter.

    The default value is 1. You can purchase up to 20 instances at a time. Specify the number of instances based on your business requirements.

14. Confirm the order information, quantity, and Subscription Duration (only for subscription RDS instances), select Service Agreement, click Pay, and then complete the payment. The console displays Payment Successful or Activated.

    Note

    For a subscription RDS instance, we recommend that you select Auto-Renew to prevent service interruptions due to unintended subscription expiration.

    The auto-renewal cycle is one month for monthly subscription and one year for yearly subscription. The actual auto-renewal cycle in the order prevails. You can disable auto-renewal at any time. For more information, see Auto-renewal.

15. View the RDS instance.

    Go to the Instances page, select the region in which the RDS instance resides from the top of the page, and then find the RDS instance based on the Creation Time parameter.

    Note

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

Old version of the ApsaraDB RDS buy page

Step 1: Configure basic settings

1. Open the ApsaraDB RDS buy page of the old version.

2. Configure the Billing Method parameter.

   Billing Method	Recommendation	Benefit
   Subscription	For long-term use, select Subscription (pay in advance) and configure the Subscription Duration parameter in the lower-left corner of the page.	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-Go	For short-term use, select Pay-As-You-Go (billed by hour). You can create a pay-as-you-go RDS instance and switch the billing method of the RDS instance to subscription after you confirm that the RDS instance meets your requirements.	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 RDS instance.
   Serverless	If you need to process scheduled tasks, handle fluctuating workloads, use fully managed services, or eliminate the need for O&M, select Serverless. Note For more information about serverless RDS instances and how to create serverless RDS instances, see Serverless ApsaraDB RDS for MySQL.	You are charged based on the on-demand resources that are used to run your workloads. This significantly reduces 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 select the region in which your ECS instance resides for the RDS instance. 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 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 of your ECS instance, see Preparations.

   • 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. This way, you can connect to the RDS instance from your application by using the public endpoint of the instance.

4. Configure the Database Engine, Edition, Product Type, and Storage Type parameters.

   1. Configure the Database Engine parameter.

      This topic describes how to create an ApsaraDB RDS for MySQL instance. Select MySQL. We recommend that you select MySQL 8.0 or select the database engine version that is run on your self-managed MySQL instance. The default value of this parameter is 8.0.

      Note

      • Serverless RDS instances support MySQL 5.7 and MySQL 8.0.

      • For more information about the lifecycle of MySQL major versions, see Lifecycle of MySQL major versions.

   2. Select Product Series.

      Edition	Description	Feature
      Basic Edition	A node.	RDS Basic Edition is cost-effective and is suitable for learning and testing. RDS instances that run RDS Basic Edition require a long period of time to restart or recover from faults.
      High-availability Edition	In RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance. 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 in production environments.
      Cluster Edition (Recommended)	In RDS Cluster Edition, the database system consists of a primary node and multiple secondary nodes.	In RDS Cluster Edition, primary and secondary nodes work in HA mode and the secondary nodes are readable.

      Note

      • The available RDS editions vary based on the region and database engine that you select.

      • RDS Cluster Edition supports MySQL 8.0 and MySQL 5.7.

      • For more information about RDS editions, see Overview of ApsaraDB RDS editions.

   3. Configure the Product Type parameter. You can select Standard or YiTian. For more information, see Product types.

      Note

      • YiTian RDS instances support MySQL 8.0 and MySQL 5.7.

      • If your RDS instance runs RDS Basic Edition, you do not need to configure this parameter.

   4. Configure the Storage Type parameter.

      Comparison item	Enhanced SSD	Premium Performance Disk (Recommended)	Local SSD
      Elastic Scalability	★★★★★ Maximum storage capacity: 64,000 GB. No transient connections occur during storage expansion. You can upgrade, downgrade, create, or release the RDS instance within minutes. Automatic storage expansion is supported.	★★★★★ If your RDS instance runs MySQL or PostgreSQL, online storage capacity expansion is supported, and you can expand the storage capacity of your RDS instance within a few seconds.	★★ Maximum storage capacity: 8,000 GB. Transient connections occur during storage expansion. The upgrade, downgrade, creation, or release of an RDS instance may require several hours. The automatic storage expansion feature is not supported.
      Performance	★★★★★ PL1<PL2<PL3 An enhanced SSD (ESSD) of performance level 2 (PL2) provides twice the IOPS and throughput of a PL1 ESSD. A PL3 ESSD delivers IOPS that is up to 20 times the IOPS delivered by a PL1 ESSD. A PL3 ESSD also delivers throughput that is up to 11 times the throughput delivered by a PL1 ESSD. Note ApsaraDB RDS provides three storage types. For more information, see Storage types.	★★★★★★ Premium performance disks are compatible with all features of ESSDs. Premium performance disks provide higher baseline I/O performance than PL1 ESSDs. Premium performance disks also provide the I/O burst, Buffer Pool Extension (BPE), and data archiving features. For more information, see What are premium performance disks? and Improvement in baseline I/O performance of premium performance disks for ApsaraDB RDS.	★★★★★ Reduces I/O latencies and improves I/O performance.
      Backup	★★★★★ A backup can be completed within minutes or seconds. The highest backup frequency is one backup every 15 minutes.	★★★★★ A backup can be completed within minutes or seconds. The highest backup frequency is one backup every 15 minutes.	★★★ A backup requires a long period of time to complete. The highest backup frequency is one backup every day.

      Note

      • If your RDS instance runs MySQL 8.0 or MySQL 5.7 and RDS Basic Edition, the RDS instance supports only cloud disks. If your RDS instance runs MySQL 5.6 or MySQL 5.5 and RDS High-availability Edition, the RDS instance supports only local SSDs. Serverless RDS instances support only cloud disks.

      • For more information about the differences between cloud disks and local SSDs, see Features of ApsaraDB RDS for MySQL.

   5. (Optional) If you select a cloud disk for your RDS instance, you can enable disk encryption.

5. Select a zone in which you want to create the instance.

   Each zone is an independent physical location within a region. For example, the China (Hangzhou) region contains Zone H, Zone I, and Zone J.

   • Select a zone

     • All zones in a region provide the same services.

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

   • Deployment Method

     • Multi-zone Deployment (recommended): The primary node and secondary node are deployed in different zones in the same region. This deployment method provides cross-zone disaster recovery.

       If you select Multi-zone Deployment, you must configure the Primary Zone and Secondary Zone parameters.

     • Single-zone Deployment: The primary node and secondary node are deployed in the same zone.

       If you set the Edition parameter to Basic Edition, you can select only Single-zone Deployment.

     Note

     • For an RDS instance that consists of primary and secondary nodes, we recommend that you select Multi-zone Deployment to implement cross-zone disaster recovery.

     • If you set the Edition parameter to Cluster Edition, you must also specify the number of secondary nodes and the zones in which the primary and secondary nodes are deployed.

6. Configure the Instance Type parameter.

   1. Configure the Type parameter (General-purpose or Dedicated).

      Type	Description	Feature
      General-purpose	A general-purpose RDS instance exclusively occupies the allocated memory and I/O resources. Shared: CPU and storage	General-purpose RDS instances are cost-effective.
      Dedicated	A dedicated RDS instance occupies all 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 occupies all CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.	A dedicated RDS instance can deliver 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 CPU cores and memory capacity. For more information about instance types, see Primary instance types of ApsaraDB RDS for MySQL.

      • 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

      If you set the Edition parameter to Cluster Edition, the Pricing column displays the price per node in the cluster. If you purchase one primary node and two secondary nodes for the cluster, the price of the cluster is triple the price that is displayed in the Pricing column.

7. Configure the Storage Capacity parameter.

   The valid values of the Storage 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.

   Note

   If you select RDS High-availability Edition and a cloud disk, you can select Enable Automatic Storage Expansion and configure the trigger condition and upper limit for automatic storage expansion. If automatic storage expansion is triggered, the system automatically increases the storage capacity based on the larger value between 5 GB and 15% of the current storage capacity. This helps prevent the RDS instance from being locked due to insufficient storage resources.

8. (Optional) If you select Subscription and Local SSD, you must configure the Backup Retention Policy After Release parameter. We recommend that you select Retain Last Backup or Retain All Backups to prevent data loss due to unintended subscription expiration. For more information, see Long-term backup retention.

9. (Optional) If it is a Subscription instance, you need to select the Subscription Duration.

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

Step 2: Instance Configuration

1. Configure the network of the RDS instance. The Network Type parameter is set to VPC by default.

   1. Configure the VPC and Primary Zone VSwitch parameters.

      Note

      We recommend that you select the same virtual private cloud (VPC) in which your ECS instance resides for your RDS instance. If you select a different VPC for your RDS instance, you cannot connect your RDS instance and ECS instance over an internal network.

   2. Specify whether to Add VPC CIDR Block To Whitelist.

      Note

      If you set this parameter to No, you can manually configure a whitelist after the RDS instance is created. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for MySQL instance.

   3. Configure the Port parameter.

      You can initialize the port when you create an RDS instance. Valid values: 1000 to 65534.

2. Configure custom parameters. If you do not have special requirements, you can retain the default values.

   Parameter	Description
   Default Storage Engine	InnoDB: an open source default storage engine that can provide comprehensive features. This is the recommended storage engine. X-Engine: a storage engine that is developed by Alibaba. X-Engine is compatible with InnoDB and provides a high compression ratio. X-Engine can save more than 60% of storage space. Note This parameter is available only when you select MySQL 8.0, High-availability Edition or Basic Edition in the previous step.
   Parameter Template	Select the high-performance, asynchronous, default, or custom parameter template based on your business requirements. The parameters in the parameter template are displayed on the right. For more information, see Use a parameter template. Note This parameter is available only when you select High-availability Edition or Basic Edition in the previous step.
   Time Zone	Select a time zone for your RDS instance. Note This parameter is available only when you select High-availability Edition or Basic Edition in the previous step.
   Table Name Case Sensitivity	The default value is Case-insensitive. If your self-managed database is case-sensitive to table names, you can set this parameter to Case-sensitive to facilitate data migration. Note This parameter is available only when you select High-availability Edition or Basic Edition in the previous step.
   Release Protection	Specify 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 instance.
   Minor Version Upgrade Policy	Configure a policy based on which the minor engine version of the RDS instance is updated: Auto Upgrade (recommended): The system automatically upgrades the minor engine version of the RDS instance to the latest version during the maintenance window. You can modify the upgrade time on the Scheduled Events page. Manual Upgrade: You can manually upgrade the minor engine version of the RDS instance on the Basic Information page of the RDS instance. If you do not want to use the latest minor engine version, you can select Select Minor Version to specify a minor engine version.
   Instance Description	Enter a description for easy identification.
   Tag	You can add tags to distinguish multiple RDS instances to facilitate instance management. For more information, see Filter ApsaraDB RDS instances by tag.
   Resource Group	Use the default resource group or select a custom resource group based on your business requirements. This facilitates instance management.
   Privileged Account	You can select Set Now to create a privileged account by specifying an account name and a password. You can also click Set Later to create a privileged account after the RDS instance is created. For more information about privileged accounts, see Create a privileged account.

3. In the lower-right corner of the page, click Next: Confirm Order.

Step 3: Confirm Order

1. Confirm the order information, Quantity, and Subscription Duration (only for subscription RDS instances), select Service Agreement, click Pay, and then complete the payment. The console displays Payment Successful or Activated.

   Note

   For a subscription RDS instance, we recommend that you select Auto-Renew to prevent service interruptions due to unintended subscription expiration.

   The auto-renewal cycle is one month for monthly subscription and one year for yearly subscription. The actual auto-renewal cycle in the order prevails. You can disable auto-renewal at any time. For more information, see Auto-renewal.

2. View the RDS instance.

   Go to the Instances page, select the region in which the RDS instance resides from the top of the page, and then find the RDS instance based on the Creation Time parameter.

   Note

   It takes 1 to 10 minutes to create an RDS instance. You can refresh the page to view the RDS instance.