Quickly create an ApsaraDB RDS for PostgreSQL instance

New version

1. Open the ApsaraDB RDS buy page (new version).

2. Set the Billing Method.

   To create a Serverless instance, see Create a serverless ApsaraDB RDS for PostgreSQL instance. The total price appears in the lower-right corner after all required parameters are set.

   Billing method	Best for	How you're charged
   Subscription	Long-running workloads	Upfront fee; lower unit cost for longer terms
   Pay-as-you-go	Short-term or variable workloads	Hourly, based on actual usage; billing stops immediately on release
   Serverless	Workloads with unpredictable peaks	Based on resource consumption; CPU and memory scale automatically

3. Set the Region.

   • To connect this instance to an Elastic Compute Service (ECS) instance over the internal network, select the region where the ECS instance resides. Instances in different regions cannot communicate over the internal network.

   • If your application runs on an on-premises server, select the region geographically closest to that server. Connect using the instance's public endpoint.

   Important

   The region cannot be changed after the instance is created.

4. Set the Database Engine, SLR Authorization, Edition, Product Type, and Storage Type.

   1. Set Database Engine to PostgreSQL and select the version that fits your requirements. > Note: ApsaraDB RDS for PostgreSQL includes Babelfish, which enables instances running PostgreSQL 13, 14, or 15 to accept T-SQL statements. If you need to connect a SQL Server application or client to a PostgreSQL instance, select Enable Babelfish during creation. See Introduction to Babelfish.

   2. Set SLR Authorization. If this is your first time creating an RDS for PostgreSQL instance, click Authorize to grant the AliyunServiceRoleForRdsPgsqlOnEcs service-linked role (SLR). This allows the instance to attach Elastic Network Interfaces (ENIs) and establish network connections. Authorization is required only once and incurs no charges.

   3. Set the Edition.

      Edition	Architecture	Suitable for
      Basic Edition	Single primary instance	Personal learning, microsites, dev/test environments for small and medium-sized enterprises. Restart and fault recovery take longer than other editions.
      High-availability Edition	Primary + secondary instance in HA mode; supports read-only instances	Production databases for large and medium-sized enterprises; internet, IoT, e-commerce, logistics, gaming
      Cluster Edition (recommended)	Primary node + multiple readable secondary nodes in HA mode	Production databases for large and medium-sized enterprises; internet-based new retail, automotive, ERP systems

      Note

      Note: Available editions vary by region and PostgreSQL version. See Overview of ApsaraDB RDS editions.

   4. Set Product Type. Valid values: Standard and YiTian. > Note: This parameter does not apply to Basic Edition. For High-availability Edition and Cluster Edition, see Product types.

   5. Set Storage Type.

      	ESSD (recommended)	General ESSD
      Scalability	Up to 64 TB; no transient connections during expansion; automatic storage expansion supported	Online expansion in seconds
      Performance	PL1 < PL2 < PL3. PL2 delivers 2x the IOPS and throughput of PL1. PL3 delivers up to 20x the IOPS and 11x the throughput of PL1.	Higher baseline I/O than PL1 ESSD; supports I/O burst, I/O acceleration, and data archiving
      Backup frequency	Up to once every 15 minutes	Up to once every 15 minutes

      Note

      Note: Available storage types vary by database engine and edition. For ESSD or General ESSD, enable Cloud Disk Encryption to protect data at rest. See Use the cloud disk encryption feature and General ESSDs.

5. Set the Network Type (fixed as VPC).

   1. Set VPC. For the instance to communicate with an ECS instance over the internal network, both must reside in the same region and the same virtual private cloud (VPC). Instances in different VPCs cannot connect over the internal network, even within the same region. > Note: Instances in the same VPC can connect over the internal network even if they use different vSwitches.

   2. Set Add to Whitelist.

      • Yes: The CIDR block of the selected VPC is added to the instance whitelist, allowing ECS instances in that VPC to connect.

      • No: Configure the whitelist after creation. See Configure an IP address whitelist.

6. Select a zone, a vSwitch, and a Deployment Method.

   • Zone: No substantive difference exists between zones in the same region. For best performance, place the RDS instance in the same zone as the ECS instance running your application. Cross-zone instances in the same region perform slightly lower than same-zone instances.

   • vSwitch: Select an existing vSwitch or click Create vSwitch. See Create and manage a vSwitch.

   • Deployment Method:

     Method	Description
     Multi-zone Deployment (recommended)	Primary and secondary instances reside in different zones, providing zone-level disaster recovery. Configure Zone and Network of Primary Node and Zone and Network of Secondary Node.
     Single-zone Deployment	Primary and secondary instances share the same zone. Basic Edition supports this method only.

   If a zone shows Sold Out, it lacks sufficient resources. Select a different zone.

7. Set the Instance Type.

   1. Set Category.

      Category	Resources	Best for
      General-purpose	Exclusively owns memory and I/O; shares CPU and storage with other instances on the same host	Cost-sensitive workloads
      Dedicated	Exclusively owns CPU, memory, storage, and I/O. The dedicated host subtype exclusively owns all resources on the physical host.	Performance-sensitive or stability-critical workloads. Not available for Basic Edition.

   2. Select a specific instance type (CPU cores, memory, max connections, max IOPS). See Primary ApsaraDB RDS instance types for the full list.

      • Test environments: 2+ cores

      • Production environments: 4+ cores

8. Set the Storage Capacity. The available range depends on the instance type and storage type. Adjust in 5 GB increments.

9. (Subscription only) Set the Subscription Duration.

   • Baseline Price: The list price without discounts.

   • Preferential Monthly Fee: The monthly price derived from the baseline price.

   • Price: Hover over View Details on the right to see the estimated total based on duration and baseline price.

   Displayed prices are based on list price only and exclude coupons or promotions.

10. (Optional) Configure additional parameters. Default values work for most use cases. The minor engine version follows this format:

    Parameter	Description
    Port	Port for the instance. Valid values: 1000–5999. Default: 5432.
    Parameter Template	Apply a parameter template at creation time. If none is selected, the default system template is used. See Use a parameter template.
    Release Protection	Pay-as-you-go instances only. Prevents accidental release. See Enable or disable release protection.
    Minor Engine Version Update Policy	Defaults to Automatic Upgrade. When the minor engine version is outdated, the system schedules an O&M task within your configured maintenance window and notifies you by email or internal message. Pin a specific AliPG minor version at creation time; if none is specified, the latest AliPG version is used. See Release notes for AliPG. After creation, modify this setting on the Basic Information page. See Update the minor engine version.
    Resource Group	The resource group for this instance. Retain the default or select a custom group.
    Babelfish Migration Mode	Applies only when Enable Babelfish is selected. Choose single-db (one SQL Server database per instance, standard PostgreSQL schema) or multi-db (multiple SQL Server databases, schemas named <Database name>_<Schema name>). See Migration modes.
    Initial Account	(Babelfish only) Username for the Babelfish management account used to connect over the TDS port. This is a privileged account and cannot be deleted after creation.
    Password	(Babelfish only) Password for the Babelfish management account. See Reset a password.
    Time Zone	Configurable on the primary instance only; read-only instances inherit the primary's time zone. The time zone is not in UTC. If not specified, the region's default time zone is applied. See Common time zones and Region-to-time-zone mappings.
    Instance Description	A custom name to help identify the instance.
    Tags	Add tags to distinguish and filter instances. See Use tags to filter instances.
    Privileged Account	Create a privileged account now, or select Configure Later to do it after creation. See Create a database and an account.

    Field	Description	Example
    rds	RDS instance	—
    postgres	PostgreSQL database	—
    1400	Major PostgreSQL version	14
    20220830	AliPG version	20220830
    14.4	Minor PostgreSQL version	14.4

     rds_postgres_1400_20220830_14.4

    With Babelfish enabled, the format is:

     rds_postgres_1400_20220630_babelfish_14.4

11. In the upper-right corner, set Quantity (default: 1; maximum: 20 per purchase).

12. Review the configuration, read and accept the ApsaraDB RDS Terms of Service, then click Pay Now to complete payment. For Subscription instances, also confirm the subscription duration. The console displays Congratulations or The service is activated when the instance is ready.

    For Subscription instances, enable Auto-renewal to prevent service interruptions if you forget to renew. The auto-renewal cycle matches your subscription term: one month for monthly subscriptions, one year for yearly subscriptions. Disable auto-renewal at any time. See Use the auto-renewal feature.

13. Go to the Instances page. In the top navigation bar, select the region where you created the instance, then find it by Creation Time.

    Instance creation takes 1–10 minutes. Refresh the page if the instance is not yet visible.

Old version