All Products
Search

This Product

    PolarDB:Create a PolarDB-X instance

    Document Center

    PolarDB:Create a PolarDB-X instance

    Last Updated:Mar 30, 2026

    Create a PolarDB-X 2.0 instance from the console in a few steps. Instance creation takes 10 to 15 minutes.

    Prerequisites

    Before you begin, ensure that you have:

    • A Virtual Private Cloud (VPC) in the same region and zone where you plan to deploy the instance. If you don't have one, create a VPC.

    • A vSwitch in the target VPC. If you don't have one, create a vSwitch.

    • (Optional) If you plan to access the instance from an Elastic Compute Service (ECS) instance, make sure the ECS instance and the PolarDB-X instance are in the same VPC.

    Create an instance

    1. Log on to the PolarDB-X console.

    2. In the top navigation bar, select the region where you want to deploy the instance.

    3. On the Instances page, click the PolarDB-X 2.0 tab.

    4. In the upper-right corner of the page, click Create Instance.

    5. On the buy page, configure the parameters described in the following sections, then click Buy Now.

    6. On the Confirm Order page, read and agree to the terms of service, then click Pay.

    After payment, the system takes 10 to 15 minutes to create the instance. When the instance is ready, view it on the Instance List page.

    Parameter reference

    Billing and purchase

    Parameter Description
    Product Type The billing type. Select PolarDB-X 2.0 Prepay for subscription billing or PolarDB-X 2.0 Postpay for pay-as-you-go billing. PolarDB-X 1.0 (Subscription) is also available.
    Quantity The number of instances to purchase.
    Subscription Duration The subscription period. Available only for subscription instances. Enable Auto-renewal to automatically renew the instance before it expires.

    Choosing a billing type

    Subscription Pay-as-you-go
    Charged At purchase Hourly
    Best for Long-term, stable workloads Short-term or variable workloads
    Cost Lower unit cost Higher unit cost, release anytime to stop charges
    Requirement — Account balance ≥ USD 100

    Deployment

    Parameter Description
    Regions and Zones The region where the instance is deployed.
    Create Type How to create the instance: Create by Default creates a new instance; Migrate from ApsaraDB RDS migrates an existing RDS instance to PolarDB-X. If you select the migration option, also specify the Source RDS Version (MySQL 5.6, 5.7, or 8.0) and the Source RDS Instance.
    Topology The node deployment topology. See the topology comparison below.
    Primary Node Zone The zone for the primary node.
    Secondary Node Zone The zone for the secondary nodes. Available only when Topology is set to Three-zone Deployment.
    Logger Node Zone The zone for the logger nodes. Available only when Topology is set to Three-zone Deployment.

    Choosing a topology

    Single-zone deployment Three-zone deployment
    Zone configuration Specify one zone; primary, secondary, and logger nodes are deployed in the same zone Specify separate zones for the primary, secondary, and logger nodes
    Disaster recovery Within a single zone Cross-zone, at no additional charge

    Network

    Parameter Description
    Network Type The network type. Defaults to VPC.
    VPC The VPC for the instance.
    vSwitch The vSwitch for the instance.

    Instance edition and compute

    Parameter Description
    Compatibility The MySQL compatibility version. Valid values: MySQL 5.7 and MySQL 8.0.
    Edition The instance edition. Enterprise Edition is distributed; Standard Edition is centralized.
    Instance Purchase Type Set automatically based on the edition: User Defined for Enterprise Edition, Default for Standard Edition.
    Instance Family General-purpose: shares idle CPU resources with other instances on the same server, optimizing cost. Dedicated: exclusively allocates CPU resources to the instance, improving stability.
    CN Node Spec The specifications for compute nodes (CN nodes). CN nodes provide a stateless distributed SQL engine that handles query routing, optimization, and execution. They use two-phase commit (2PC) to coordinate distributed transactions and execute DDL statements across shards.
    DN Node Spec The specifications for data nodes (DN nodes). DN nodes provide the storage engine. They use the majority-based Paxos consensus protocol for high-availability storage and Multi-Version Concurrency Control (MVCC) for distributed transactions. DN nodes also support pushdown computation for Project, Filter, Join, and Agg operators, and support local SSDs and shared storage.
    CN Nodes The number of compute nodes.
    DN Nodes The number of data nodes.
    Node Specifications The node specifications. Available only when Edition is set to Standard Edition.

    Storage

    Parameter Description
    Storage Type The storage type for the instance. Local SSD-Custom: specify a fixed disk size per data node. Local SSD: no disk size configuration needed; charged hourly based on actual usage, rounded up to the nearest hour.
    Storage Node Disk The disk size per data node. Available only when Storage Type is set to Local SSD-Custom.

    What's next