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

Note You are offered a reduced price on your first purchase of an RDS instance. For more information, visit the ApsaraDB RDS promotion page.

Prerequisites

The AliyunRDSFullAccess policy is attached to the RAM user that you used to create an RDS instance. For more information, see Use RAM for resource authorization.

Procedure

  1. Go to the ApsaraDB RDS buy page.
  2. Configure the Billing Method parameter.
    Billing method Description Benefit
    Subscription A subscription instance is an instance for which you pay an upfront fee. If you want to use an instance for a long period of time, we recommend that you select the Subscription billing method. If you select the subscription billing method, configure the Duration parameter in the lower part of the page. In most cases, the subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term usage. Alibaba Cloud provides lower prices for longer subscription periods.
    Pay-As-You-Go You are charged on an hourly basis for a pay-as-you-go instance based on your actual resource usage. If you want to use an instance for a short period of time, we recommend that you select the Pay-As-You-Go billing method.

    You can create a pay-as-you-go RDS instance. After you confirm that the new RDS instance meets your business requirements, you can change the billing method of the RDS instance from pay-as-you-go to subscription.

    You can release a pay-as-you-go RDS instance based on your business requirements. The billing cycle of a pay-as-you-go RDS instance immediately stops after you release the instance.
    Note You can view the price in the lower-right corner of the page. The price is displayed only after you configure all required parameters.
  3. Configure the following parameters.
    Parameter Description
    Region The region where the RDS instance resides.

    We recommend that you select the region of the Elastic Compute Service (ECS) instance on which your application is deployed. If the RDS instance and the ECS instance reside in different regions, you cannot connect these instances over an internal network. In this case, these instances cannot deliver the optimal performance.

    Note
    • After an RDS instance is created, you cannot change the region of the RDS instance. If you want to connect an ECS instance and an RDS instance over an internal network, make sure that the RDS instance and the ECS instance reside in the same region.
    • For more information about how to view the region in which an ECS instance resides, see Get ready to use ApsaraDB RDS for MySQL.
    • If your application is deployed on an on-premises server or on-premises computer, we recommend that you select a region that is near your on-premises server or on-premises computer. This way, you can use the public endpoint of the RDS instance to connect to the RDS instance from your application.
    Database Engine The database engine and version that are run by the RDS instance. Select PostgreSQL. The supported PostgreSQL versions are 10, 11, 12, 13, and 14.
    Note The available database engines and versions vary based on the region that you select.
    Edition
    • Basic: In RDS Basic Edition, the database system consists of only a primary RDS instance. RDS Basic Edition is cost-effective and is suitable for learning and testing.
      Note RDS instances that run RDS Basic Edition require a long period of time to restart or recover from faults.
    • High-availability: This is the recommended edition. In RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance. These instances work in the high availability architecture. RDS High-availability Edition is suitable for production environments, and is suitable for more than 80% of business scenarios.
    Note
    Storage Type
    • Local SSD: A local SSD resides on the same host as the database engine. You can store data on local SSDs to reduce I/O latency. Local SSDs are supported only for RDS instances that run PostgreSQL 10.
    • ESSD: Enhanced SSDs (ESSDs) come in three performance levels (PLs).
      • ESSD PL1: This is the basic PL of ESSDs.
      • ESSD PL2: An ESSD of PL2 delivers IOPS and throughput that are approximately two times the IOPS and throughput delivered by an ESSD of PL1.
      • ESSD PL3: An ESSD of PL3 delivers IOPS that is up to 20 times the IOPS delivered by an ESSD of PL1. An ESSD of PL3 also delivers throughput that is up to 11 times higher than the throughput delivered by an ESSD of PL1. ESSDs of PL3 are suitable for business scenarios in which highly concurrent requests must be processed with high I/O performance and at low read and write latencies.
    • Standard SSD: A standard SSD is an elastic block storage device that is designed based on the distributed storage architecture. You can store data on standard SSDs to separate computing from storage.
    Note
    Deployment Method

    Select a zone where the RDS instance resides.

    • Multi-zone Deployment: This is the recommended deployment method. The primary RDS instance and the secondary RDS instance reside in different zones to provide zone-disaster recovery.
    • Single-zone Deployment: The primary RDS instance and the secondary RDS instance reside in the same zone.
    Note
    • No substantive differences exist between the zones in the same region.
    • If the RDS instance resides in the same zone as the ECS instance on which your application is deployed, these instances can deliver optimal performance. If the RDS instance and the ECS instance reside in different zones in the same region, the performance of the RDS instance and the ECS instance is slightly lower than the performance of the RDS instance and the ECS instance that reside in the same zone.
    • If you select RDS Basic Edition, you can select only the Single-zone Deployment method.
    Instance Type The instance type of the RDS instance. Before you select an instance type, you must select an instance family.
    • General-purpose (Entry-level): specifies the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same physical host.
    • Dedicated (Enterprise-level): A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. Dedicated host instance types provide the highest specifications in the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources on the physical host on which the instance is deployed.
    Note For information, see Primary ApsaraDB RDS instance types.
    Capacity The storage capacity that is provided to store data files, system files, binary log files, and transaction files in the RDS instance. You can adjust the storage capacity at a step size of 5 GB.
    Note If you select the local SSD storage type, the storage capacity of the RDS instance may vary based on the instance type. If you select the standard SSD or ESSD storage type, the storage capacity of the RDS instance does not vary based on the instance type. For information, see Primary ApsaraDB RDS instance types.
  4. In the lower-right corner of the page, click Next: Instance Configuration.
  5. Specify the network type of the RDS instance.
    1. Network Type: If your application is deployed on an ECS instance, the network type of the ECS instance and the RDS instance must be the same. Otherwise, you cannot connect the ECS instance and the RDS instance over an internal network.
      Note
      • For more information about how to view the network type of the ECS instance, see Get ready to use ApsaraDB RDS for MySQL.
      • If you do not want to connect the ECS instance and the RDS instance over an internal network, you can select the classic network type or the VPC network type.
      • Some RDS instances do not support the classic network type.
    2. VPC and vSwitch: If you select the VPC network type, you must also select a VPC and a vSwitch. We recommend that you select the VPC of the ECS instance on which your application is deployed. If the RDS instance and the ECS instance reside in different VPCs, you cannot connect these instances over an internal network.
      Note
      • For more information about how to view the VPC in which your ECS instance resides, see Get ready to use ApsaraDB RDS for MySQL.
      • You can connect the RDS instance and the ECS instance over an internal network even if the instances use different vSwitches in the same VPC.
  6. Configure more custom parameters. If you do not have special business requirements, you can retain the default values of these parameters.
    Parameter Description
    Release Protection Specifies whether to enable the release protection feature. The release protection feature is used to prevent a pay-as-you-go RDS instance from being released due to unintended operations. For more information, see Enable or disable the release protection feature for an ApsaraDB RDS for MySQL instance.
    Resource Group The resource group to which the RDS instance belongs. You can retain the default resource group or select a custom resource group based on your business requirements.
    Time Zone The time zone of the RDS instance.
    Note
  7. In the lower-right corner of the page, click Next: Confirm Order.
  8. Confirm the configuration of the RDS instance in the Parameters section, configure the Purchase Plan and Duration parameters, read and select Terms of Service, and then click Pay Now. You must configure the Duration parameter only if you select the subscription billing method for the RDS instance.
    Note If you select the subscription billing method for the RDS instance, we recommend that you select Auto-Renew Enabled. This way, you can prevent interruptions to your workloads even if you forget to review the RDS instance.
  9. View the RDS instance.
    Open the Instances page. In the top navigation bar, select the region where the RDS instance resides. Then, find the RDS instance based on the Creation Time.

What to do next

Create a database and an account on an ApsaraDB RDS for PostgreSQL instance

FAQ

Why am I unable to find the RDS instance that I created?

Possible cause Description Suggestion
Incorrect region The RDS instance does not reside in the region that you selected. In the top navigation bar, select the region where the RDS instance resides. Then, you can find the RDS instance.
Insufficient resources The zone that you selected cannot provide sufficient resources.

If the RDS instance cannot be created, you can go to the Orders page in the Billing Management console to view the refunded fee.

We recommend that you select a different zone and try again.
RAM policies that do not allow users to create unencrypted RDS instances RAM policies that do not allow users to create unencrypted RDS instances are attached to RAM users.
  • If you use the credentials of a RAM user to create an RDS instance that uses local SSDs, the RDS instance cannot be created. When you create an RDS instance that uses local SSDs, you cannot enable disk encryption.
  • If you use the credentials of a RAM user to create an RDS instance that uses standard SSDs or ESSDs and you do not enable disk encryption for the RDS instance, the RDS instance cannot be created.

For more information, see Use RAM policies to manage the permissions of RAM users on ApsaraDB RDS instances.

When you create an RDS instance, select the standard SSD or ESSD storage type, select Disk Encryption, set the Key parameter, and then try again.

References