This topic describes how to purchase a pay-as-you-go cluster in the PolarDB console.

Note If you use an ApsaraDB RDS for MySQL instance, you can create a ApsaraDB PolarDB MySQL-compatible edition cluster by using the Migration from RDS method. The created PolarDB cluster retains the accounts, databases, IP address whitelist, and required parameters of the source ApsaraDB RDS for MySQL instance. For more information, see Create a PolarDB for MySQL cluster from an ApsaraDB RDS for MySQL instance.

Prerequisites

An Alibaba Cloud account is created and is used to log on to the Alibaba Cloud Management Console. For more information, see Register and log on to an Alibaba Cloud account.

Background information

ApsaraDB PolarDB MySQL-compatible edition clusters support three editions: Cluster Edition, Single Node, and Archive Database. For more information about each edition, see Product editions.

Note
  • PolarDB supports virtual private clouds (VPCs). A VPC is an isolated network on Alibaba Cloud. It provides extra protection and is more secure than the classic network.
  • To optimize the performance of PolarDB, you can deploy PolarDB clusters and other Alibaba Cloud services in the same internal network. We recommend that you deploy PolarDB clusters and Elastic Compute Service (ECS) instances in the same VPC to ensure the optimal performance of PolarDB. If your ECS instance is deployed in the classic network, you must migrate the instance to a VPC.

Procedure

  1. Log on to the PolarDB console.
  2. In the upper-left corner of the page, click Create Cluster.
  3. Specify Pay-As-You-Go as the value of the Product Type parameter.
  4. Specify the following parameters.
    Parameter Description
    Region The region where the cluster resides. You cannot change the region after you purchase the cluster.
    Note Make sure that the PolarDB cluster to be created and the Elastic Compute Service (ECS) instance to be connected are deployed in the same virtual private cloud (VPC). Otherwise, the cluster and the ECS instance cannot communicate over the internal network to achieve the optimal performance.
    Create Type The method to create a PolarDB cluster.
    • Create Primary Cluster: creates a PolarDB cluster.
    • Create Secondary Cluster: creates a secondary cluster that is deployed in a global database network (GDN). For more information, see Add a secondary cluster.
    • Migration from RDS: clones the data of an ApsaraDB RDS for MySQL instance and keeps synchronizing incremental data from the ApsaraDB RDS for MySQL instance to the PolarDB for MySQL cluster. This method is often used for migration. The read/write status of the PolarDB cluster is Read Only before data migration is started. By default, the binary logging is enabled. For more information, see Create a PolarDB for MySQL cluster from an ApsaraDB RDS for MySQL instance.
      • RDS Engine Type: the engine type of the source ApsaraDB RDS for MySQL instance. The value of this parameter can be only MySQL. You do not need to select the value of this parameter.
      • RDS Engine Version: the version of the source ApsaraDB RDS for MySQL instance. You can select 5.6 or 5.7.
      • Source RDS Instance: the available source ApsaraDB RDS for MySQL instances that exclude read-only instances.
        Note The list of available source instances excludes read-only instances. You cannot select the ApsaraDB RDS for MySQL instances where the TDE or SSL feature is enabled and data is not stored in the InnoDB storage engine. When you restore data from a backup file to PolarDB, the source instance runs as expected.
    • Clone from RDS: creates a PolarDB cluster by cloning the data of an RDS instance in a quick way. For more information, see Create a PolarDB for MySQL cluster by using the Clone from RDS method.
      • RDS Engine Type: the engine type of the source ApsaraDB RDS for MySQL instance. The value of this parameter can be only MySQL. You do not need to select the value of this parameter.
      • RDS Engine Version: the version of the source ApsaraDB RDS for MySQL instance. You can select 5.6 or 5.7.
      • Source RDS Instance: the available source ApsaraDB RDS for MySQL instances that exclude read-only instances.
        Note The list of available source instances excludes read-only instances. You cannot select the ApsaraDB RDS for MySQL instances where the TDE or SSL feature is enabled and data is not stored in the InnoDB storage engine. When you restore data from a backup file to PolarDB, the source instance runs as expected.
    • Restore from Recycle: creates a cluster by restoring a backup file of a deleted cluster from the recycle bin.
      • Source Version: the version of the cluster that has been deleted.
      • Deleted Clusters: the name of the cluster that has been deleted.
      • Backup History: the backup that you want to restore.
    Primary Availability Zone The primary zone of the cluster.
    • A zone is an independent geographical location that resides in a region. No substantial differences exist between different zones.
    • You can choose to create your PolarDB cluster in the same zone as the Elastic Compute Service (ECS) instance or in the zone that is different from the instance zone.
    • You need only to select the primary zone. The system automatically selects a secondary zone.
    Network Type The value of this parameter can be only VPC. You do not need to select the value of this parameter.
    Note Before you use the classic network, select a VPC. After the cluster is created, configure the classic network. For more information, see VPC-facing endpoints and public-facing endpoints.
    VPC

    VSwitch

    Make sure that the PolarDB cluster to be created and the ECS instance to be connected are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over the internal network to achieve the optimal performance.
    • If you have created a VPC that meets your network plan, select the VPC. For example, if you have created an ECS instance and the VPC where the ECS instance resides meets your network plan, select this VPC.
    • If you do not create a VPC that meets your network plan, use the default VPC and the default vSwitch.
      • Default VPC:
        • The default VPC is a unique VPC in the selected region.
        • The subnet mask consists of 16 bits, such as 172.168.0.0/16. A maximum of 65,536 private IP addresses can be provided.
        • The default VPC is not included in the VPC quota that Alibaba Cloud assigns to you.
      • Default vSwitch:
        • The default vSwitch is a unique vSwitch in your selected zone.
        • The subnet mask consists of 20 bits, such as 172.168.0.0/20. A maximum of 4,096 private IP addresses can be provided.
        • The default vSwitch is not included in the quota of vSwitches that you can create in a VPC.
    • If the default VPC and vSwitch cannot meet your requirements, you can create your own VPC and vSwitch. For more information, see Create a VPC.
    Compatibility
    • MySQL 8.0: fully compatible with MySQL 8.0. MySQL 8.0 supports parallel queries. In specific scenarios such as TPC-H tests, the performance increases by 10 times. For more information, see Parallel query.
    • MySQL 5.7: fully compatible with MySQL 5.7.
    • MySQL 5.6: fully compatible with MySQL 5.6.
    • PostgreSQL 11: fully compatible with PostgreSQL 11.
    • Compatible with Oracle Syntax: highly compatible with the Oracle syntax. For more information, see High compatibility.
    Edition
    You can select Cluster (2-16 Nodes) (Recommended), Archive Database (High Compression Ratio), or Single Node (Starter). For more information about the three editions, see Product editions.
    Note
    • You can select the Single Node (Starter) edition only when the Create Type parameter is set to Create Primary Cluster and the Compatibility parameter is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6.
    • You can select the Archive Database (High Compression Ratio) edition only when the Create Type parameter is set to Create Primary Cluster and the Compatibility parameter is set to MySQL 8.0.
    Node Specification
    • If your selected cluster edition is Cluster (2-16 Nodes) (Recommended) or Archive Database (High Compression Ratio), you can select the node specifications based on your requirements. All the nodes are dedicated nodes whose performance is stable and reliable.
    • If your selected cluster edition is Single Node (Starter), the value of this parameter can be only 4 Core, 8 GB (Burstable Performance). This value cannot be changed.

    For more information about compute node specifications, see Specifications of compute nodes.

    Nodes
    • If your source cluster edition is Cluster (2-16 Nodes) (Recommended), the system creates the following two nodes that have the same specification by default: a primary node and a read-only node. You do not need to select the value of this parameter.
      Note If the primary node becomes faulty, the system uses the read-only node as the primary node and generates another read-only node. For more information about read-only nodes, see Architecture.
    • If your source cluster edition is Single Node (Starter) or Archive Database (High Compression Ratio), the system creates a node (a primary node) by default. You do not need to select the value of this parameter.
    Storage Cost You do not need to select the value of this parameter. The system charges you on an hourly basis based on the actual data usage. For more information, see Storage pricing.
    Note You do not need to select a storage capacity when you create a cluster. The system automatically scales the storage capacity when the amount of data is increased or decreased.
    Time Zone The time zone of the cluster. The default time zone is UTC+08:00.
    Note This configuration is supported only when the Compatibility parameter is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster.
    Table Name Case Sensitivity Specifies whether table names of the cluster are case-sensitive. You can select Not Case-sensitive (Default). When the local database is case sensitive, you can select Case-sensitive. This ensures that you can migrate data in an easy way.
    Note
    • This configuration is supported only when the Compatibility parameter is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster.
    • The value of this parameter cannot be changed after the cluster is created. Proceed with caution.
    Release Cluster The backup retention policy that is used after the cluster is deleted or released. The default value is Retain Last Automatic Backup (Automatic Backup before Release).
    • Retain Last Automatic Backup (Automatic Backup before Release): retains the last backup after you delete the cluster.
    • Retain All Backups: retains all the backups after you delete the cluster.
    • Delete All Backups (Cannot be Restored): retains no backups after you delete the cluster.
    Note
    • This configuration is supported only when the Compatibility parameter is set to MySQL 8.0, MySQL 5.7, or MySQL 5.6 for the PolarDB cluster.
    • If you need to retain backups after you delete or release the cluster, you may need to pay a few fees. You can delete the backups to reduce costs. For more information, see Billing rules for data backup.
    Enable TDE Specifies whether to enable TDE. After TDE is enabled, PolarDB encrypts the data files of your cluster. This operation is transparent to service access. The performance is reduced by 5% to 10%.
    Note
    • This configuration is supported only when the Compatibility parameter is set to PostgreSQL 11 or Compatible with Oracle Syntax.
    • If the Compatibility parameter for a cluster is set to MySQL 8.0, MySQL 5.7, and MySQL 5.6, you can create the cluster and then enable the TDE feature. For more information about this operation, see Configure TDE.
    • You cannot disable the TDE feature after the TDE feature is enabled.
    Cluster Name The name of the cluster. The name must meet the following requirements:
    • It cannot start with http:// or https://.
    • It must be 2 to 256 characters in length.

    If this parameter is left empty, the system automatically generates a cluster name. You can change the cluster name after the cluster is created.

    Resource Group Select a required resource group from created resource groups. For more information about how to create a resource group, see Create a resource group.
    Note A resource group is a container that contains a group of resources in an Alibaba Cloud account. You can perform centralized management on these resources. A resource belongs to only one resource group. For more information, see Use RAM to create and authorize resource groups.
  5. Specify the Number parameter and click Buy Now.
    Note You can create a maximum of 50 clusters at a time. This allows you to create multiple clusters in specific scenarios. For example, you can enable multiple game servers at a time.
  6. On the Confirm Order page, confirm your order information. Read and accept the terms of service, and then click Activate Now.

    After you complete the activation, it takes 10 to 15 minutes to create the cluster. Then, the newly created cluster is displayed on the Clusters page.

    Note
    • If nodes in the cluster are in the Creating state, the cluster is being created and unavailable. The cluster is available only if it is in the Running state.
    • Make sure that you have selected the region where the cluster is deployed. Otherwise, you cannot view the cluster.
    • We recommend that you purchase subscription PolarDB storage plans to store a large amount of data. Storage plans are more cost-effective than pay-as-you-go storage. You are offered larger discounts if you purchase storage plans that provide larger storage capacities. For more information, see Together with storage plans.

What to do next

Configure an IP whitelist

Related operations

API Description
CreateDBCluster Creates a PolarDB cluster.
DescribeDBClusters Queries PolarDB clusters.
DescribeDBClusterAttribute Queries the information about a specified PolarDB cluster.