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

Prerequisites

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

Procedure

Step 1: Basic Configurations

  1. Go to the ApsaraDB RDS buy page.
  2. Configure the Billing Method parameter.
    Billing methodDescriptionBenefit
    SubscriptionA subscription RDS instance is an instance for which you pay an upfront fee. If you want to use an RDS 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. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are offered lower prices for longer subscription periods.
    Pay-as-you-goYou are charged an hourly fee for a pay-as-you-go RDS instance based on your actual resource usage. If you want to use an RDS 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 RDS instance that you created 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 Region parameter.
    The region in which 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 of an ECS instance, see Get ready to use ApsaraDB RDS for MySQL.
    • If your application is deployed on an on-premises server or computer, we recommend that you select a region that is near your on-premises server or computer. This way, you can use the public endpoint of the RDS instance to connect to the RDS instance from your application.
  4. Configure the Database Engine, Edition, Architecture and Storage Type parameters.
    1. Configure the Database Engine parameter.
      The type and version of the database engine. Select PostgreSQL. The supported PostgreSQL versions are 10, 11, 12, 13, 14 and 15.
      Note ApsaraDB RDS for PostgreSQL provides the Babelfish feature that is developed based on the Babelfish for PostgreSQL open source project. This feature enables your RDS instance that runs PostgreSQL 13 or PostgreSQL 14 to be compatible with Transact-SQL (T-SQL) statements. If you want to connect your SQL Server application or client to an RDS instance that runs PostgreSQL, we recommend that you select Enable Babelfish when you create the RDS instance. For more information, see Introduction to Babelfish.
    2. Configure the Edition parameter.
      EditionDescriptionBenefit
      BasicIn 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 scenarios.
      Note RDS instances that run RDS Basic Edition require a long period of time to restart or recover from faults.
      High-availabilityThis is the recommended RDS edition. In RDS High-availability Edition, the database system consists of a primary RDS instance and a secondary RDS instance. The primary and secondary RDS instances work in the high availability architecture. You can create read-only RDS instances and attach the read-only RDS instances to the primary RDS instance. RDS High-availability Edition is suitable for production environments and is suitable for more than 80% of business scenarios.
      Note
      • The valid values of the Edition parameter vary based on the values of the Region and Database Engine parameters that you specify.
      • For more information, see Overview of ApsaraDB RDS editions.
    3. Configure the Architecture parameter. (X86 or ARM)
      Note For more information about x86 and ARM architectures, see Architectures.
    4. Configure the Storage Type parameter.
      Comparison itemESSD (recommended)Local SSD
      Scalability★★★★★
      • You can increase the storage capacity up to 32 TB.
      • No transient connections occur during storage expansion.
      • You can upgrade, downgrade, create, or release the RDS instance within minutes.
      • Automatic storage expansion is supported.
      ★★
      • You can increase the storage capacity up to 6 TB.
      • Transient connections occur during storage expansion.
      • A few hours may be required to upgrade, downgrade, create, or release the RDS instance.
      • Automatic storage expansion is not supported.
      Performance★★★★★
      • PL1<PL2<PL3
      • An ESSD of PL2 delivers IOPS and throughput that are up to two times the IOPS and throughput delivered by an ESSD of PL1.
      • 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 the throughput delivered by an ESSD of PL1.
      Note ApsaraDB RDS provides three storage types. For more information, see Storage types.
      ★★★★★
      Backup★★★★★
      • A backup can be completed within minutes or seconds.
      • The highest backup frequency is once every 15 minutes.
      ★★★
      • A backup requires a long period of time to complete.
      • The highest backup frequency is once every day.
      Note
      • The valid values of the Storage Type parameter vary based on the values of the Database Engine and Edition parameters that you specify.
      • For more information about storage types, see Storage types.
  5. Select a zone in which the RDS instance resides.Then, configure the Deployment Method parameter.
    • Select a zone.
      • No significant 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 the 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.
    • Select a deployment method.
      • 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.

        If you select Multi-zone Deployment for the Deployment Method parameter, you must configure the Zone of Primary Node and Zone of Secondary Node parameters.

      • Single-zone Deployment: The primary RDS instance and the secondary RDS instance reside in the same zone.

        If you set Edition to Basic, only the Single-zone Deployment method is available.

      Note If Sold Out appears in the upper-right corner of a zone name, this zone does not have sufficient resources. Switch to another zone.
  6. Configure the Instance Type parameter.
    1. Configure the Category parameter. You can select General-purpose or Dedicated.
      CategoryDescriptionBenefit
      General-purposeA general-purpose RDS instance occupies all the allocated memory and I/O resources.

      A general-purpose RDS instance shares CPU and storage resources with other general-purpose RDS instances that are deployed on the same host.

      General-purpose RDS instances are cost-effective.
      DedicatedA dedicated RDS instance occupies all the allocated CPU, memory, storage, and I/O resources.
      Note The dedicated host instance family is the highest configuration of the dedicated instance family. A dedicated host RDS instance occupies all CPU, memory, storage, and I/O resources of the host on which the RDS instance is deployed.
      A dedicated RDS instance provides higher performance and higher stability.
      Note An RDS instance that runs RDS Basic Edition does not support the dedicated instance family.
      Note ApsaraDB RDS for PostgreSQL instances that use the new architecture are available for purchase. The new architecture provides better scalability and higher performance. In addition, the new architecture accelerates instance creation and instance specification changes. The new architecture for RDS instances is in development. Some features of ApsaraDB RDS are not supported for RDS instances that use the new architecture. For more information, see Primary RDS instances of the new general-purpose instance types.
    2. Configure detailed specifications, such as the number of cores, memory capacity, maximum number of connections, and maximum IOPS.
      • In a test environment, we recommend that you select an instance type that provides two or more cores.
      • In a production environment, we recommend that you select an instance type that provides four or more cores.
      Note For more information, see Primary ApsaraDB RDS instance types.
  7. Configure the Capacity parameter.
    The valid values of the Capacity parameter vary based on the values of the Storage Type and Instance Type parameters that you specify. You can adjust the storage capacity at a step size of 5 GB.
  8. Optional. If you set Billing Method to Subscription, configure the Duration parameter based on your business requirements.
  9. In the lower-right corner of the page, click Next:Instance Configuration.

Step 2: Instance Configuration

  1. Configure the Network Type parameter.
    1. Configure the Network Type parameter of the RDS instance.
      • If you select the standard SSD or ESSD storage type for the RDS instance, only the VPC option is supported.
      • If you select the local SSD storage type for the RDS instance, both the Classic network and VPC options are supported. 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.
    2. Configure the VPC and VSwitch of Primary Node parameters.
      If you set Network Type to VPC, 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 you select a different VPC for your RDS instance, you cannot connect your RDS instance and ECS instance 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.
      • If you set Deployment Method to Multi-zone Deployment in the Basic Configurations step, you must also configure the VSwitch of Secondary Node parameter.
    3. Configure the Add to Whitelist parameter to specify whether to add the CIDR block of the selected VPC to a whitelist of the RDS instance.
      If you select Yes for the Add to Whitelist parameter, the ECS instances that reside in the selected VPC can access the RDS instance.
      Note If you select No for the Add to Whitelist parameter, you can configure a whitelist after the RDS instance is created. For more information, see Configure an IP address whitelist for an ApsaraDB RDS for PostgreSQL instance.
  2. Configure the Parameter Template parameter.
    If you set Storage Type to ESSD PL1, ESSD PL2, or ESSD PL3, you can specify a parameter template when you create an RDS instance. If you do not specify a parameter template, the default system parameter template is used. You can create a custom parameter template. For more information, see Use a parameter template to configure the parameters of ApsaraDB RDS for PostgreSQL instances.
  3. Configure the Release Protection parameter.
    If you set Billing Method to Pay-As-You-Go, you can enable Release Protection for the RDS instance to prevent the 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.
  4. Configure the Minor Version Upgrade Policy parameter.
    The policy that is used to update the minor engine version of the RDS instance. You can select a minor engine version when you create the RDS instance. If you do not select a minor engine version, the latest version of AliPG is used by default.
    Example:
    rds_postgres_1400_20220830_14.4
    The following list describes the fields in the preceding example:
    • rds: RDS instance.
    • postgres: PostgreSQL database.
    • 1400: the major version of PostgreSQL, which is 14 in this example.
    • 20220830: the version of AliPG. You can select 20220130 or later. For more information, see Release notes for AliSQL.
    • 14.4: the minor version of PostgreSQL, which is 14.4 in this example.
    Note If you select Enable Babelfish in the Basic Configurations step, the minor engine version of the RDS instance is displayed in the following format:
    rds_postgres_1400_20220630_babelfish_14.4
    • If your RDS instance runs PostgreSQL 13, you can select the AliPG version of 20220228 or later.
    • If your RDS instance runs PostgreSQL 14, you can select the AliPG version of 20220630 or later.
  5. Configure the Resource Group parameter.
    Use the default resource group or select a custom resource group based on your business requirements.
  6. Optional. Configure the Babelfish-related parameters.
    The following parameters take effect only when you select Enable Babelfish in the Basic Configurations step.
    • Babelfish Migration Mode: the migration mode for the RDS instance for which Babelfish is enabled.
      • single-db: You can create only one SQL Server database on an RDS instance for which Babelfish is enabled and create a standard PostgreSQL schema for the database.
      • multi-db: You can create multiple SQL Server databases and create different PostgreSQL schemas for the databases. You must name the schemas in the <Database name>_<Schema name> format to prevent name conflicts.
      Note For more information, see Migration modes.
    • Initial Account: the username of the Babelfish management account that is used to connect to the RDS instance over the TDS port.
      Important This account is a privileged account and cannot be deleted after it is created.
    • Password: the password of the Babelfish management account.
      Note You can change the password after the RDS instance is created. For more information, see Reset the password of an account on an ApsaraDB RDS for PostgreSQL instance.
  7. Configure the Time Zone parameter.
  8. Configure the SLR Authorization parameter.
    If this is the first time you create an RDS instance after October 10, 2022, you must create the AliyunServiceRoleForRdsPgsqlOnEcs service-linked role (SLR) for ApsaraDB RDS for PostgreSQL. This way, your RDS instance can mount Elastic Network Interfaces (ENIs) and establish network connections.
    Note
  9. Configure the Privileged Account parameter.
    You can create a privileged account when you create an RDS instance. If you select Later, you can create a privileged account after the RDS instance is created.
    Note For more information about privileged accounts and how to create privileged accounts, see Create a database and an account on an ApsaraDB RDS for PostgreSQL instance.
  10. In the lower-right corner of the page, click Next:Confirm Order.

Step 3: Confirm Order

  1. 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 when 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 on your workloads even if you forget to renew the RDS instance.
  2. View your RDS instance.
    Open the Instances page. In the top navigation bar, select the region in which 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 causeDescriptionSuggestion
Incorrect regionThe RDS instance does not reside in the region that you selected. In the top navigation bar, select the region in which the RDS instance resides. Then, you can find the RDS instance.
Insufficient resourcesThe 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 fees.

We recommend that you select a different zone and try again.
RAM policies that do not allow users to create unencrypted RDS instancesRAM 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 Key, and then try again.

References