PolarDB:Custom purchase

Enterprise Edition

1. Go to the custom purchase page for PolarDB clusters and configure the following parameters.

   Category	Parameter	Description
   Billing Method		Subscription: This is an upfront billing method. When you create a cluster, you select resources with defined specifications and pay for them in advance. The longer the subscription duration, the larger the discount. This billing method is suitable for long-term, stable business requirements. Pay-as-you-go: This is a post-paid billing method. When you create a cluster, you select resources with defined specifications but do not need to pay for them in advance. You are billed based on the actual usage duration. This billing method is suitable for flexible business requirements. Note If you find that the current billing method for your PolarDB cluster does not meet your business needs, you can change the billing method at any time as needed.
   Region		Select the geographic location of the cluster. You cannot change the region after the cluster is purchased. For more information, see Regions and zones. Note Ensure that the PolarDB cluster and the ECS instance that you want to connect to are in the same region. Otherwise, they cannot use the internal network for communication and must use the internet, which prevents optimal performance. You can create the PolarDB cluster and the ECS instance in the same zone or in different zones. Creating the PolarDB cluster and the ECS instance in the same zone reduces network latency and improves access speed.
   Creation Method		Select a method to create the PolarDB cluster. Create Primary Cluster: Creates a new PolarDB cluster. Restore From Recycle Bin: You can create a new cluster by restoring a backup of a deleted cluster from the recycle bin. Original Version: The version of the deleted cluster. Deleted Cluster: The name of the deleted cluster. Historical Backup: Select the backup that you want to restore. Migrate From RDS: This method first clones data from an RDS instance and then maintains incremental synchronization. It is mainly used for migration. Before the final migration switchover, the PolarDB cluster is read-only, and binary logging is enabled by default. For more information, see Solution overview. Source RDS Version: The version of the source RDS instance. You can select PostgreSQL 9, PostgreSQL 10, PostgreSQL 11, PostgreSQL 12, PostgreSQL 13, PostgreSQL 14, PostgreSQL 15, or PostgreSQL 16. Source RDS Instance: The optional source RDS instance. Read-only instances are not included. Note Other options are used to create databases of other engines.
   Engine And Version	Database Engine	Select a Database Engine. PolarDB for PostgreSQL supports the following database engines: PostgreSQL 17 PostgreSQL 16 PostgreSQL 15 PostgreSQL 14 PostgreSQL 11
   	Edition	Set Edition to Enterprise Edition.
   	Series	Fixed to Cluster Edition (Recommended).
   	Sub-series	Supports two sub-series: General-purpose and Dedicated. Dedicated: Each cluster exclusively uses its allocated compute resources, such as CPU, without sharing them with other clusters on the same server. This provides more stable and reliable performance. General-purpose: Different clusters on the same server make full use of each other's idle compute resources, such as CPU. This resource reuse offers cost savings and higher cost-effectiveness.
   	CPU Architecture	Fixed to X86.
   Network And Zone	Primary Zone	Select the Primary Zone for the cluster. A zone is an independent physical area within a region. There are no substantial differences between zones. You can create the PolarDB cluster and the ECS instance in the same zone or in different zones.
   	Network Type	Configure the VPC and vSwitch. The network type is fixed to VPC and does not need to be selected. Ensure that the PolarDB cluster and the ECS instance that you want to connect to are in the same VPC. Otherwise, they cannot use the internal network for communication, which prevents optimal performance. If you have already created a VPC that meets your network planning needs, select that VPC. For example, if you have an ECS instance in a VPC that meets your needs, select that VPC. If you have not created a suitable VPC, you can use the default VPC and vSwitch: Default VPC: It is unique within your selected region. The CIDR block mask is 16 bits, such as 192.168.0.0/16, which can provide up to 65,536 private IP addresses. It does not consume your VPC quota. Default vSwitch: It is unique within your selected zone. The CIDR block mask is 20 bits, such as 192.168.0.0/20, which can provide up to 4,096 private IP addresses. It does not consume the quota for creating vSwitches in the VPC. If the default VPC and vSwitch do not meet your requirements, you can create a VPC and a vSwitch. For more information, see Create and manage a VPC.
   	High-availability Mode	Select a High-availability Mode. Dual-zone (Hot Standby Storage Cluster Enabled): PolarDB deploys a primary cluster (including mutually backed-up compute nodes and primary storage) and a hot standby storage cluster in the same region. Both the primary cluster and the hot standby storage cluster maintain three data replicas (a total of six replicas), providing a higher SLA for reliability. Single-zone (Hot Standby Storage Cluster Disabled): Only the primary cluster (with three data replicas) is retained. The storage unit price is half that of the dual-zone option. The cluster's SLA is also lower. Note For more information about the hot standby storage cluster and its solutions, see High-availability Mode.
   	Secondary Zone	Select a Secondary Zone. This parameter is required only when you set High-availability Mode to Dual-zone (Hot Standby Storage Cluster Enabled). Automatic Allocation is supported.
   Specifications And Proxy	Node Specifications	Select the specifications for the cluster's compute nodes. Note For more information about compute node specifications, see Enterprise Edition compute node specifications.
   	Number Of Nodes	The system displays two nodes by default (one read/write node and one read-only node). You can select two nodes (one read/write and one read-only) or one node (read/write node).
   Storage	Storage Type	PolarDB supports two storage types: PSL5 and PSL4. PSL5: A storage type supported by historical versions of PolarDB. It offers good performance, high reliability, and high availability. PSL4: A new storage type for PolarDB that uses Alibaba Cloud's self-developed smart-SSD technology. This technology compresses and decompresses data at the physical SSD level. It keeps the performance impact manageable while lowering the storage price per unit of data. Note You cannot switch the storage type for an existing cluster. To switch the storage type, purchase a new cluster with the desired storage type and migrate the data from the original cluster to the new one. For a detailed comparison of the two storage types, see How to choose between PSL4 and PSL5.
   	Storage Billing Method	PolarDB supports two storage billing methods: Billed By Capacity (Pay-as-you-go) and Billed By Space (Subscription). Billed By Capacity (Pay-as-you-go): This is a serverless billing method for storage. You do not need to specify a storage capacity at the time of purchase. The storage automatically scales out as your data grows, and you are charged only for the actual storage space used. Billed By Space (Subscription): You must pay for the storage space of the cluster upfront at the time of purchase. For more information about the two storage billing methods, see Storage billing methods. Note This parameter is supported only when Billing Method is set to Subscription.
   	Storage Capacity	The storage capacity to purchase for the "Billed by space (Subscription)" method. The storage capacity ranges from 10 GB to 500 TB. The minimum adjustment increment is 10 GB. Note This parameter is supported only when Billing Method is set to Subscription and Storage Billing Method is set to Billed By Space (Subscription).
   	Storage Fees	No selection is required. The system bills you hourly based on your actual data usage. For more information, see Specifications and pricing. Note You do not need to select a storage capacity when creating a cluster. The storage capacity scales automatically with the amount of data.
   Advanced Options (Optional)	Cluster Name	Choose to have the Cluster Name automatically generated or customize it. If you choose to have the Cluster Name automatically generated, the system will generate a name after the cluster is created. You can modify the auto-generated name. If you choose to customize the Cluster Name, you must enter a name that meets the following requirements: It cannot start with http:// or https://. It must be 2 to 256 characters in length. It must start with an uppercase letter, a lowercase letter, or a Chinese character. It can contain digits, periods (.), underscores (_), or hyphens (-).
   	Resource Group	Select a target resource group from your created resource groups. Note A resource group is a container that lets you manage a group of related resources under a single Alibaba Cloud account. A resource can belong to only one resource group. For more information, see Resource groups and authorization.
   	Enable TDE	Select whether to enable TDE. After you enable TDE, PolarDB encrypts the cluster's data files. This process is transparent to your applications but may cause a 5% to 10% performance loss. Note You cannot disable TDE after it is enabled. TDE depends on the KMS service. After enabling TDE, you must configure a service role and authorize PolarDB to access KMS.

2. On the right side of the page, confirm that all configurations, such as Billing Method, Region, Deployment Mode, and Resource Group, meet your business requirements. Then, configure the following parameters:

   Parameter	Description
   Quantity	Select the number of clusters to purchase. Note You can create up to 50 clusters at a time. This is suitable for business scenarios such as launching multiple game servers in batches. Your Alibaba Cloud account can have a maximum of 50 clusters.
   Subscription Duration	If the billing method is Subscription, you must configure the Subscription Duration for the cluster and select whether to Enable Auto-renewal. Note We recommend that you select Enable Auto-renewal to avoid business interruptions caused by a forgotten renewal.

   Review the total cost and the detailed cost breakdown (such as compute specifications, storage, and network). Click Buy Now. This action confirms that you have read and agree to the Terms of Service and any product-specific terms for your selected configuration. On the Payment page, confirm the unpaid order information, select a payment method, and click Pay.

After the purchase is successful, it takes 10 to 15 minutes to create the cluster. You can then find the newly created cluster in the cluster list.

Standard Edition

1. Go to the custom purchase page for PolarDB clusters and configure the following parameters.

   Category	Parameter	Description
   Billing Method		Subscription: This is an upfront billing method. When you create a cluster, you select resources with defined specifications and pay for them in advance. The longer the subscription duration, the larger the discount. This billing method is suitable for long-term, stable business requirements. Pay-as-you-go: This is a post-paid billing method. When you create a cluster, you select resources with defined specifications but do not need to pay for them in advance. You are billed based on the actual usage duration. This billing method is suitable for flexible business requirements. Serverless: This is a post-paid billing method. When you create a cluster, you do not need to select resources with defined specifications or pay for them in advance. This mode provides dynamic scalability for PolarDB clusters, allowing them to adjust based on changes in system workload. It is suitable for scenarios with fluctuating, uncertain, or unpredictable business workloads. Note If you find that the current billing method for your PolarDB cluster does not meet your business needs, you can change the billing method at any time as needed.
   Region		Select the geographic location of the cluster. You cannot change the region after the cluster is purchased. For more information, see Regions and zones. Note Ensure that the PolarDB cluster and the ECS instance that you want to connect to are in the same region. Otherwise, they cannot use the internal network for communication and must use the internet, which prevents optimal performance. You can create the PolarDB cluster and the ECS instance in the same zone or in different zones. Creating the PolarDB cluster and the ECS instance in the same zone reduces network latency and improves access speed.
   Creation Method		Select a method to create the PolarDB cluster. Create Primary Cluster: Creates a new PolarDB cluster. Restore From Recycle Bin: You can create a new cluster by restoring a backup of a deleted cluster from the recycle bin. Original Version: The version of the deleted cluster. Deleted Cluster: The name of the deleted cluster. Historical Backup: Select the backup that you want to restore. Migrate from RDS: This method first clones data from an RDS instance and then maintains incremental synchronization. It is mainly used for migration. Before the final migration switchover, the PolarDB cluster is read-only, and binary logging is enabled by default. Source RDS Version: The version of the source RDS instance. You can select PostgreSQL 9, PostgreSQL 10, PostgreSQL 11, PostgreSQL 12, PostgreSQL 13, PostgreSQL 14, PostgreSQL 15, or PostgreSQL 16. Source RDS Instance: The optional source RDS instance. Read-only instances are not included. Note Other options are used to create databases of other engines.
   Engine And Version	Database Engine	Select a Database Engine. The following database engines are supported: PostgreSQL 16 PostgreSQL 15 PostgreSQL 14
   	Edition	Set Edition to Standard Edition.
   	Sub-series	Supports two sub-series: General-purpose and Dedicated. Dedicated: Each cluster exclusively uses its allocated compute resources, such as CPU, without sharing them with other clusters on the same server. This provides more stable and reliable performance. General-purpose: Different clusters on the same server make full use of each other's idle compute resources, such as CPU. This resource reuse offers cost savings and higher cost-effectiveness.
   	CPU Architecture	Set CPU Architecture to X86 or Yitian ARM. X86: The X86 architecture uses Intel processors and high-performance networks to deliver comprehensively improved performance and stability. It meets the requirements of enterprise applications that demand high business stability and computing performance. ARM: The ARM architecture uses Alibaba Cloud's self-developed Yitian 710 processor chip and 25 GE intelligent high-speed network interface cards to provide powerful computing capabilities. Paired with a high-performance network, it better meets the cost-effectiveness, security, and stability requirements for cloud-based services of various enterprises, including government and internet companies.
   Network And Zone	Primary Zone	Select the Primary Zone for the cluster. A zone is an independent physical area within a region. There are no substantial differences between zones. You can create the PolarDB cluster and the ECS instance in the same zone or in different zones.
   	Network Type	Configure the VPC and vSwitch. The network type is fixed to VPC and does not need to be selected. Ensure that the PolarDB cluster and the ECS instance that you want to connect to are in the same VPC. Otherwise, they cannot use the internal network for communication, which prevents optimal performance. If you have already created a VPC that meets your network planning needs, select that VPC. For example, if you have an ECS instance in a VPC that meets your needs, select that VPC. If you have not created a suitable VPC, you can use the default VPC and vSwitch: Default VPC: It is unique within your selected region. The CIDR block mask is 16 bits, such as 192.168.0.0/16, which can provide up to 65,536 private IP addresses. It does not consume your VPC quota. Default vSwitch: It is unique within your selected zone. The CIDR block mask is 20 bits, such as 192.168.0.0/20, which can provide up to 4,096 private IP addresses. It does not consume the quota for creating vSwitches in the VPC. If the default VPC and vSwitch do not meet your requirements, you can create a VPC and a vSwitch. For more information, see Create and manage a VPC.
   	High-availability Model	Select a High-availability Mode. Dual-zone (Hot Standby Storage Cluster Enabled): PolarDB deploys a primary cluster (including mutually backed-up compute nodes and primary storage) and a hot standby storage cluster in the same region. Both the primary cluster and the hot standby storage cluster maintain three data replicas (a total of six replicas), providing a higher SLA for reliability. Single-zone (Hot Standby Storage Cluster Disabled): Only the primary cluster (with three data replicas) is retained. The storage unit price is half that of the dual-zone option. The cluster's SLA is also lower. Note For more information about the hot standby storage cluster and its solutions, see High-availability Mode.
   	Secondary Zone	Select a Secondary Zone. This parameter is required only when you set High-availability Mode to Dual-zone (Hot Standby Storage Cluster Enabled). Automatic Allocation is supported.
   Specifications And Proxy	Node Specifications	Select the specifications for the cluster's compute nodes. Note For more information about compute node specifications, see Enterprise Edition compute node specifications.
   	Number Of Nodes	The system displays two nodes by default (one read/write node and one read-only node). You can select two nodes (one read/write and one read-only) or one node (read/write node).
   	Database Proxy Type	Two database proxy types are supported: Standard Enterprise Edition and Dedicated Enterprise Edition. This is associated with the cluster sub-series. Standard Enterprise Edition: Corresponds to the General-purpose sub-series of the cluster. It can share physical CPU resources and provide intelligent, second-level resource scalability based on the business workload. Dedicated Enterprise Edition: Corresponds to the Dedicated sub-series of the cluster. It exclusively uses physical CPU resources for better performance stability.
   	Proxy Specifications	Choose to disable the database proxy or configure its specifications separately. The database proxy specifications can be configured from 4 cores to 64 cores (4 vCPUs to 64 vCPUs). Auto-matching is also supported.
   Storage	Storage Type	Select a Storage Type. An enterprise SSD (ESSD) is an ultra-high performance disk product launched by Alibaba Cloud. Based on the next-generation distributed block storage architecture, combined with 25 GE networking and RDMA technology, ESSDs provide up to 1 million random read/write IOPS per disk and lower single-path latency. ESSDs are categorized as follows: PL0 ESSD: An ESSD of performance level 0 (PL0). PL1 ESSD: Compared to a PL0 ESSD, a PL1 ESSD can increase IOPS by 5 times and throughput by about 2 times. PL2 ESSD: Compared to a PL1 ESSD, a PL2 ESSD can increase IOPS and throughput by about 2 times. PL3 ESSD: Compared to a PL2 ESSD, a PL3 ESSD can increase IOPS by up to 10 times and throughput by 5 times. It is suitable for business scenarios that require extremely high concurrent I/O performance and extremely stable read/write latency. ESSD AutoPL Disk: Compared to PL0, PL1, PL2, and PL3 ESSDs, IOPS is decoupled from capacity, allowing for flexible configuration and on-demand adjustments to reduce the overall TCO. For more information about ESSD performance, see ESSDs. Important When the storage space of a disk is full, the disk will be locked (read-only).
   	Storage Billing Method	The storage billing method follows the cluster's billing method configuration. Note This parameter is supported only when Billing Method is set to Subscription.
   	Storage Capacity	Select the Storage Capacity. The storage capacity of the ESSD to purchase. The storage capacity ranges from 20 GB to 64 TB. The minimum adjustment increment is 10 GB.
   Advanced Options (Optional)	Cluster Name	Choose to have the Cluster Name automatically generated or customize it. If you choose to have the Cluster Name automatically generated, the system will generate a name after the cluster is created. You can modify the auto-generated name. If you choose to customize the Cluster Name, you must enter a name that meets the following requirements: It cannot start with http:// or https://. It must be 2 to 256 characters in length. It must start with an uppercase letter, a lowercase letter, or a Chinese character. It can contain digits, periods (.), underscores (_), or hyphens (-).
   	Resource Group	Select a target resource group from your created resource groups. Note A resource group is a container that lets you manage a group of related resources under a single Alibaba Cloud account. A resource can belong to only one resource group. For more information, see Resource groups and authorization.
   	Enable TDE	Select whether to enable TDE. After you enable TDE, PolarDB encrypts the cluster's data files. This process is transparent to your applications but may cause a 5% to 10% performance loss. Note You cannot disable TDE after it is enabled. TDE depends on the KMS service. After enabling TDE, you must configure a service role and authorize PolarDB to access KMS.

2. On the right side of the page, confirm that all configurations, such as Billing Method, Region, Deployment Mode, and Resource Group, meet your business requirements. Then, configure the following parameters:

   Parameter	Description
   Quantity	Select the number of clusters to purchase. Note You can create up to 50 clusters at a time. This is suitable for business scenarios such as launching multiple game servers in batches. Your Alibaba Cloud account can have a maximum of 50 clusters.
   Subscription Duration	If the billing method is Subscription, you must configure the Subscription Duration for the cluster and select whether to Enable Auto-renewal. Note We recommend that you select Enable Auto-renewal to avoid business interruptions caused by a forgotten renewal.

   Review the total cost and the detailed cost breakdown (such as compute specifications, storage, and network). Click Buy Now. This action confirms that you have read and agree to the Terms of Service and any product-specific terms for your selected configuration. On the Payment page, confirm the unpaid order information, select a payment method, and click Pay.

   After the purchase is successful, it takes 10 to 15 minutes to create the cluster. You can then find the newly created cluster in the cluster list.

   Note

   • If a node in the cluster has a status of Creating, the cluster is not yet available. The cluster is ready for use when its status changes to Running.

   • Make sure that you select the correct region. Otherwise, you cannot find the cluster that you created.