This topic describes how to create an ApsaraDB RDS for PostgreSQL instance in the ApsaraDB for RDS console. You can also create an ApsaraDB RDS for PostgreSQL instance by calling an API operation.

For more information, see Pricing, billing items, and billing methods.

A new ApsaraDB for RDS console is available to create instances. You can use the original or new console.

Prerequisites

  • You have an Alibaba Cloud account.

Precautions

You can create up to 30 pay-as-you-go instances in your Alibaba Cloud account. To increase this quota, you must submit a ticket.

Create an RDS instance in the new ApsaraDB for RDS console

  1. Log on to the ApsaraDB for RDS console.
    Note You can click Back to Old Version in the upper-right corner to switch to the original ApsaraDB for RDS console.
  2. Configure the following parameters.
    Parameter Description
    Billing Method
    • Subscription: You must pay the subscription fee when you create an instance. We recommend that you select subscription billing for long-term use because it is more cost-effective than pay-as-you-go billing. You receive larger discounts for longer subscription periods.
    • Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. We recommend that you select pay-as-you-go billing for short-term use. You can release your pay-as-you-go instance to reduce costs when you no longer need it.
    Region The region where the RDS instance resides.
    • You cannot change the region after you purchase the instance.
    • To maximize access speed, we recommend that you select a region in close proximity to the geographic location where your users reside.
    • Make sure that the RDS instance is created in the same region as the ECS instance to which you want to connect. If the RDS and ECS instances reside in different regions, these instances cannot communicate over an internal network and cannot deliver optimal performance.
    Database Engine The database engine and engine version that the RDS instance is running. Select PostgreSQL. Supported PostgreSQL versions are 9.4, 10, 11, and 12.
    Note The database engines that are available vary based on the region you select.
    Edition
    • Basic: The database system consists of only one instance. Computing is separated from storage to increase cost-efficiency.
    • High-availability: The database system adopts the classic high-availability architecture that consists of one primary instance and one secondary instance.
    Note The RDS editions that are available vary based on the region and database engine version you select. For more information, see ApsaraDB for RDS edition overview.
    Storage Type
    • Local SSD: A local SSD is a storage device in the node where the database engine resides. You can store data on a local SSD to reduce I/O latency.
    • Enhanced SSD: An enhanced SSD is an ultra-high performance disk provided by Alibaba Cloud based on the new generation of distributed block storage architecture. It integrates 25 Gigabit Ethernet and remote direct memory access (RDMA) technologies to reduce latency and deliver up to 1 million random input/output operations per second (IOPS). ESSDs are available in three performance levels (PLs):
      • ESSD: ESSDs of PL1.
      • ESSD PL2: provides double the amount of IOPS and throughput than an ESSD PL1.
      • ESSD PL3: provides up to 20 times of IOPS and 11 times of throughput than an ESSD PL1. It is suitable for scenarios when ultra-high concurrent IOPS and stable read/write latency are required.
    • Standard SSD: A standard SSD is an elastic block storage device designed based on the distributed storage architecture. You can store data on a standard SSD to separate computing from storage.
      Note You can select Disk Encryption when you create an instance with a standard SSD or ESSD to ensure maximum protection for your data. For more information, see Configure data encryption for an RDS PostgreSQL instance.

    For more information about storage types, see Storage types.

    Zone

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. Zone of Primary Node indicates the zone where the primary instance resides, and Zone of Secondary Node indicates the zone where the secondary instance resides.

    You can set the deployment mode of the instance to Multi-zone Deployment or Single-zone Development.

    • Single-zone Deployment indicates the Zone of Primary Node and Zone of Secondary Node are consistent.
    • Multi-zone Deployment indicates the Zone of Primary Node and Zone of Secondary Node are different. After you have selected a Zone of Primary Node, the system automatically assigns a Zone of Secondary Node.

    Multi-zone deployment provides zone-disaster recovery for your business. We recommend that you select Multi-zone Deployment.

    Note
    • High-availability instances with standard SSDs or enhanced SSDs support multi-zone deployment.
    • After you have created an instance, you can view information about the primary and secondary instances on the Service Availability page.
    • A Basic instance has one node that can be deployed in only one zone.
    Select a zone
    Instance Type
    • Entry-level: belongs to the general-purpose instance family. A general-purpose instance occupies exclusive memory and I/O resources. However, it shares CPU and storage resources with other general-purpose instances on the same server.
    • Enterprise-level: belongs to the dedicated instance family. A dedicated instance occupies exclusive CPU, memory, storage, and I/O resources allocated to it. The top configuration of the dedicated instance family is the dedicated host. A dedicated host instance occupies all CPU, memory, storage, and I/O resources on the server where it resides.
    Note Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum input/output operations per second (IOPS). For more information, see Primary instance types.
    Capacity The storage capacity that is used to store data files, system files, binlog files, and transaction files. The storage capacity increases in increments of 5 GB.
    Note The dedicated instance family supports exclusive allocations of resources. Therefore, the storage capacity of each instance type with local SSDs in this family is fixed. For more information, see Primary instance types.
  3. Click Next: Instance Configuration.
  4. Configure the following parameters.
    Parameter Description
    Network Type
    • Classic Network: a traditional type of network.
    • VPC: A virtual private cloud (VPC) is an isolated virtual network with higher security and better performance than a classic network. If you select the VPC network type, you must also specify VPC and VSwitch of Primary Node.
    Note The primary RDS instance must have the same network type as the ECS instance to which you want to connect. If both network types are VPC, make sure that they reside in the same VPC. Otherwise, these instances cannot communicate over an internal network.
    Resource Group The resource group to which the RDS instance belongs.
  5. Click Next: Confirm Order. Confirm the settings in the Parameters section, specify Purchase Plan and Duration, read and select Terms of Service, and click Pay Now. You need to specify Duration only when you create a subscription instance.

Create an RDS instance in the original ApsaraDB for RDS console

  1. Log on to the original ApsaraDB for RDS console.
  2. Select Subscription or Pay-As-You-Go. For more information about the billing methods, see .
  3. Configure the following parameters.
    Parameter Description
    Region The region where the RDS instance resides. You cannot change the region after you purchase the instance.
    • To maximize access speed, we recommend that you select a region that is located in close proximity to the geographic location where your users reside.
    • Make sure that the RDS instance is created in the same region as the ECS instance to which you want to connect. If the RDS and ECS instances reside in different regions, these instances cannot communicate over an internal network and cannot deliver optimal performance.
    Resource Group The resource group to which the RDS instance belongs.
    Database Engine

    The database engine that the RDS instance is running. Select PostgreSQL.

    Note The database engines that are available vary based on the region you select.
    Version The version of PostgreSQL.
    Note The database engine versions that are available vary based on the region you select.
    Edition
    • Basic: It consists of only one node and separates computing resources from storage resources to implement high cost-efficiency.
    • High-availability: The database system adopts the classic high-availability architecture that consists of one primary node and one secondary node.
    For more information, see ApsaraDB for RDS edition overview.

    The RDS editions that are available vary based on the database engine version you select.

    Storage Type
    • Local SSD: A local SSD is a storage device in the node where the database engine resides. You can store data on a local SSD to reduce I/O latency.
    • Standard SSD: A standard SSD is an elastic block storage device designed based on the distributed storage architecture. You can store data on a standard SSD to separate computing from storage.

    For more information, see Storage types.

    Zone

    The zone where the RDS instance resides. Each zone is an independent physical location within a region. The zones that are located in the same region are similar. You can deploy your primary and secondary instances in the same zone or in different zones.

    Multi-zone deployment provides zone-disaster recovery for your business.

    Network Type
    • Classic Network: a traditional type of network.
    • VPC (recommended): A virtual private cloud (VPC) is an isolated network with higher security and better performance than a classic network.
      Note The primary RDS instance must have the same network type as the ECS instance to which you want to connect. Otherwise, these instances cannot communicate over an internal network.
    CPU and Memory Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum input/output operations per second (IOPS). For more information, see Primary instance types.

    ApsaraDB for RDS provides the following instance families:

    • General-purpose: A general-purpose instance occupies exclusive memory and I/O resources. However, it shares CPU and storage resources with other general-purpose instances deployed on the same server.
    • Dedicated: A dedicated instance occupies exclusive CPU, memory, storage, and I/O resources.
    • Dedicated host: The top configuration of the dedicated instance family. A dedicated host instance occupies all CPU, memory, storage, and I/O resources on the server where it resides.

    For example, "8 Cores, 32 GB" is a general-purpose instance type, "8 Cores, 32 GB (Dedicated)" is a dedicated instance type, and "30 Cores, 220 GB (Dedicated Host)" is a dedicated host instance type.

    Capacity The storage capacity that is used to store data files, system files, binlog files, and transaction files.
  4. Specify Duration and Quantity, and click Buy Now. You need to specify Duration only when you create a subscription instance.
    Note
    • If you create a subscription instance, you can select Auto-renewal. The system automatically renews your subscription based on the duration that you specify. For example, if you create a three-month subscription instance with Auto-renewal selected, you are charged a three-month subscription fee for each automatic renewal.
    • If you create a subscription instance, you can click Add to Cart to add it to the shopping cart. You can click Cart later to pay for the subscription instance.
  5. On the Order Confirmation page, confirm the instance configuration, read and select Terms of Service, Service Level Agreement, and Terms of Use, and click Pay Now.

What to do next

In the upper-left corner of the console, select the region where the instance is located to view the instance that you have created.

After the RDS instance is created, you must configure whitelists and create accounts. If you want to connect to the RDS instance over the Internet, you must apply for a public endpoint. You can then connect to the instance.

Related operations

Operation Description
CreateDBInstance Creates an ApsaraDB for RDS Instance.