All Products
Search
Document Center

AnalyticDB:Create an instance

Last Updated:Nov 03, 2025

This topic describes how to create an instance in the AnalyticDB for PostgreSQL console.

Prerequisites

  • You have an Alibaba Cloud account. If not, register at the Alibaba Cloud official website to create one.

  • Authorize the service-linked role. The first time you use AnalyticDB for PostgreSQL, you must authorize a service-linked role that allows the service to access other cloud resources. The console guides you through this one-time setup:

    1. Log on to the AnalyticDB for PostgreSQL console.
    2. In the upper-right corner of the console, click Create Instance.

    3. In the Create Service Linked Role dialog box, click OK.

Free trial

Alibaba Cloud offers a free trial for instances in elastic storage mode. If you are a new user of AnalyticDB for PostgreSQL, visit Alibaba Cloud Free Tier to apply. If you are ineligible for a free trial, you can follow the steps in this guide to create an instance.

Create an instance

  1. Log on to the AnalyticDB for PostgreSQL console.
  2. In the upper-right corner of the console, click Create Instance to go to the buy page.

  3. Configure the Product Type parameter. Valid values:

    • Subscription: When you create an instance, you must pay an upfront subscription fee. This billing method is more cost-effective than pay-as-you-go for long-term use, and longer subscription durations offer lower unit prices.

    • Pay-as-you-go: Pay-as-you-go instances are billed hourly based on actual resource usage. We recommend this option for short-term use. To avoid unnecessary charges, you can release the instance when it’s no longer needed.

  4. Configure the parameters that are described in the following table.

    Parameter

    Description

    Region and Zone

    The region where your instance located.

    Note
    • After completing the purchase, you cannot change the region of the instance. To optimize database access latency, select a region closest to your application’s geographic location.

    • Make sure that the instance and any ECS instances you plan to connect to are deployed in the same region. Otherwise, they cannot communicate over the internal network and will be forced to use the public network, resulting in higher latency and reduced performance.

    Each zone is an independent physical location within a region. Zones in the same region do not have substantial differences.

    You can create the instance in the same zone as the ECS instance to which you want to connect or in a different zone.

    Instance Resource Type

    The resource type of the instance. Valid values:

    • Serverless Mode: Specify only the compute resources you need and no storage reservation is required.

    • Elastic Storage Mode: You can add nodes or increase your storage capacity.

    Note

    The resource types that are available vary based on the region and zone. If the current region and zone do not provide the required instance resource type, change the region and zone.

    For information about the resource types that are available in different regions and zones, see Instance specifications.

    Serverless Mode

    The scheduling mode for the instance in Serverless mode. Valid values:

    • Manual Scheduling: Performs resource orchestration manually based on your business requirements. For example, you can manually pause and resume the instance and perform scheduled scaling. For more information, see Manually pause and resume an instance and Manage plans.

    • Auto Scheduling: The instance can be automatically paused and resumed based on traffic detection. If no traffic is detected, the instance automatically enters the idle state, and its computing resources will incur no charges.

    Note
    • This parameter is available only for instances in Serverless mode.

    • The Serverless automatic scheduling mode of AnalyticDB for PostgreSQL is in invitational preview. To apply for invitational preview, submit a ticket.

    Maximum ACUs

    The maximum number of AnalyticDB compute units (ACUs) for the instance in Serverless auto scheduling mode. Valid values: 8 to 32, in 8 increments.

    An ACU is the unit of computing resources for AnalyticDB for PostgreSQL instances in Serverless auto scheduling mode. If your instance fails to meet computing performance requirements, you can modify the value of this parameter. For more information, see Configure instance resources.

    Note

    This parameter is available only for instances in Serverless auto scheduling mode.

    Engine Version

    The engine version of the instance. Valid values: 7.0 Standard Edition and 6.0 Standard Edition.

    Note

    You can select 7.0 Standard Edition only for instances in elastic storage mode.

    Edition

    The edition of the instance. Valid values: High-performance Edition (Basic Edition) and High-availability Edition.

    Note

    You can select High-performance Edition (Basic Edition) only when you set the Instance Resource Type parameter to Elastic Storage Mode. For more information, see High-performance Edition.

    Vector Engine Optimization

    Specifies whether to enable vector search engine optimization. Valid values:

    • Disabled (Recommended for Data Warehouses): In main-stream analysis, data warehousing, and real-time data warehousing scenarios, we recommend disabling vector search engine optimization.

    • Enabled: In AI-generated content (AIGC) and vector search scenarios, we recommend enabling vector search engine optimization.

    Vector search engine optimization can improve the performance of your instance in vector analysis, but consumes large amounts of memory resources and significantly reduces query concurrency. Please carefully evaluate the impact before enabling this feature.

    Note

    Vector search engine optimization is available only for 6.0 standard edition instances in elastic storage mode with compute nodes of 4 vCPUs and 32 GB memory or higher.

    Coordinator Node Resources

    The specifications of coordinator node resources. We recommend that you select coordinator node resources with the number of compute units (CUs) to be equal to the number of CPU cores per compute node.

    If you need more coordinator node resources, you can add more resources after you create the instance. For more information, see Manage coordinator node resources.

    Note

    This parameter is unavailable for instances in Serverless auto scheduling mode.

    Compute Node Specifications

    The specifications of compute nodes. The available specifications vary based on the resource type and edition. For more information, see Instance specifications.

    Note

    This parameter is unavailable for instances in Serverless auto scheduling mode.

    Compute Nodes

    The number of compute nodes. The instance performance increases with the number of compute nodes. The number of compute nodes that you can select varies based on the resource type and edition.

    • Serverless mode

      Valid values when Edition is set to High-availability Edition: 2 to 512, in 2 increments.

    • Elastic storage mode

      • Valid values when Edition is set to High-availability Edition: 4 to 512, in 4 increments.

      • Valid values when Edition is set to High-performance Edition (Basic Edition): 2 to 512, in 2 increments.

    Note

    This parameter is unavailable for instances in Serverless auto scheduling mode.

    Disk Storage Type

    The disk storage type. Valid values:

    • PL1 ESSD (Recommended)

    • ESSD_PL0

    • PL2 ESSD (High-throughput)

    For information about the performance differences between the disk storage types, see Block storage performance.

    Note

    This parameter is available only for instances in elastic storage mode.

    Encryption Type

    The encryption type of the instance. You can select Not Encrypted or Disk Encryption.

    Note

    This parameter is available only for instances in elastic storage mode.

    CMK

    The encryption key of disks.

    This parameter is available only when you select Elastic Storage Mode and Disk Encryption.

    Single Node Storage Capacity

    The storage capacity of each node in the instance. Unit: GB. Valid values: 50 to . The value must be a multiple of 50.

    Note

    This parameter is available only for instances in elastic storage mode.

    Network Type

    The network type of the instance. The value is automatically set to VPC.

    VPC

    The ID of the virtual private cloud (VPC) in which the instance resides.

    A VPC is an isolated virtual network that provides higher security and higher performance than the classic network. Before you configure this parameter, make sure that a VPC and a vSwitch are created in the region where you want to create the instance.

    vSwitch

    The vSwitch to which the instance is connected. If no optional vSwitches are available, you can switch to another zone or create a vSwitch in the current zone.

    Resource Group

    The resource group to which the instance belongs. For more information about resource groups, see What is Resource Management?

    Sample Data

    Specifies whether to load sample data to the instance. For information about the sample dataset, see Manage a sample dataset.

    Duration

    The subscription duration of the instance.

    Note

    This parameter is available only when you set the Product Type parameter to Subscription.

  5. Click Buy Now.

  6. On the Confirm Order page, perform the following operations based on the value of the Product Type parameter:

    • Subscription

      1. Confirm the information in the Parameters section, read and select the Terms of Service, and then click Pay.

      2. On the Purchase page, click Subscribe.

    • Pay-as-you-go

      Confirm the information in the Parameters section, read and select the Terms of Service, and then click Activate Now.

  7. After the instance is created, go to the Instances page to view the instance.

    Note

    It takes a period of time to initialize an AnalyticDB for PostgreSQL instance. You can perform operations only when the instance is in the Running state.

Related operations

Operation

Description

CreateDBInstance

Creates an AnalyticDB for PostgreSQL instance.

FAQ

What do I do if the The DBInstance vswitch id is not valid error is returned when I fail to purchase an AnalyticDB for PostgreSQL instance?

Cause: No vSwitch is selected.

Solution: Select a vSwitch that is deployed in the current VPC. If no vSwitch is available in the VPC, create a vSwitch.