This topic provides an overview of instance types for primary ApsaraDB RDS for PostgreSQL instances. The overview includes the most recent instance types, the phased-out instance types, and the specifications for each instance type.
Important For RDS instances that use standard SSDs or ESSDs, the memory includes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services. Therefore, the available memory of an RDS instance may be less than the memory capacity that is supported by the instance type. The following list describes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services:
RDS instances that use cloud disks support only the virtual private cloud (VPC) network type. If you create an RDS instance that uses cloud disks in the ApsaraDB RDS console, you must set the Network Type parameter to VPC. If you create an RDS instance that uses cloud disks by calling an operation, you must set the InstanceNetworkType parameter to VPC. For more information, see Create an instance.
Instance types
RDS instances that run RDS Basic Edition
Note If an RDS instance uses clouds disks and a dedicated instance type, the maximum IOPS of the instance is calculated by using the following formula: Actual maximum IOPS = min{Maximum IOPS, IOPS that corresponds to the maximum I/O bandwidth, Cloud disk IOPS}.
The size of an I/O operation in ApsaraDB RDS for PostgreSQL is 8 KB. IOPS that corresponds to the maximum I/O bandwidth is calculated by using the following formula: IOPS that corresponds to the maximum I/O bandwidth = Maximum I/O bandwidth in MB/s × 1024/8/8.
For more information about how to calculate the cloud disk IOPS, see Primary ApsaraDB RDS instance types.
The maximum IOPS and maximum I/O bandwidth cannot be guaranteed for RDS instances that use cloud disks and general-purpose instance types.
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
General-purpose instance family | pg.n2.2c.1m | 2 cores, 4 GB | 400 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. For more information, see Primary ApsaraDB RDS instance types. | |
pg.n4.2c.1m | 2 cores, 8 GB | 800 |
pg.n2.4c.1m | 4 cores, 8 GB | 800 |
pg.n4.4c.1m | 4 cores, 16 GB | 1,600 |
pg.n4.6c.1m | 6 cores, 24 GB | 2,400 |
pg.n4.8c.1m | 8 cores, 32 GB | 3,200 |
Dedicated instance family | pg.x8.medium.1 | 2 cores, 16 GB | 1,600 | 10,000 | 128 |
pg.x8.large.1 | 4 cores, 32 GB | 3,200 | 20,000 | 192 |
pg.x8.xlarge.1 | 8 cores, 64 GB | 6,400 | 25,000 | 256 |
pg.x4.2xlarge.1 | 16 cores, 64 GB | 6,400 | 40,000 | 384 |
pg.x8.2xlarge.1 | 16 cores, 128 GB | 12,800 | 40,000 | 384 |
pg.x4.4xlarge.1 | 32 cores, 128 GB | 12,800 | 60,000 | 640 |
pg.x8.4xlarge.1 | 32 cores, 256 GB | 25,600 | 60,000 | 640 |
RDS instances that run RDS High-availability Edition
Note If an RDS instance uses clouds disks and a dedicated instance type, the maximum IOPS of the instance is calculated by using the following formula: Actual maximum IOPS = min{Maximum IOPS, IOPS that corresponds to the maximum I/O bandwidth, Cloud disk IOPS}.
The size of an I/O operation in ApsaraDB RDS for PostgreSQL is 8 KB. IOPS that corresponds to the maximum I/O bandwidth is calculated by using the following formula: IOPS that corresponds to the maximum I/O bandwidth = Maximum I/O bandwidth in MB/s × 1024/8/8.
For more information about how to calculate the cloud disk IOPS, see Primary ApsaraDB RDS instance types.
The maximum IOPS and maximum I/O bandwidth cannot be guaranteed for RDS instances that use cloud disks and general-purpose instance types.
Instance types for the standard product type (original x86 architecture)
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
General-purpose instance family | pg.n2.2c.2m | 2 cores, 4 GB | 400 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. For more information, see Primary ApsaraDB RDS instance types. | PL1 ESSD: 20 GB to 32,000 GB PL2 ESSD: 500 GB to 32,000 GB PL3 ESSD: 1,500 GB to 32,000 GB
|
pg.n2.4c.2m | 4 cores, 8 GB | 800 |
pg.n2.8c.2m | 8 cores, 16 GB | 1,600 |
pg.n4.2c.2m | 2 cores, 8 GB | 800 |
pg.n4.4c.2m | 4 cores, 16 GB | 1,600 |
pg.n4.6c.2m | 6 cores, 24 GB | 2,400 |
pg.n4.8c.2m | 8 cores, 32 GB | 3,200 |
pg.n4.12c.2m | 12 cores, 48 GB | 4,800 |
Dedicated instance family | pg.x2.medium.2c | 2 cores, 4 GB | 400 | 10,000 | 128 |
pg.x4.medium.2c | 2 cores, 8 GB | 800 | 10,000 | 128 |
pg.x8.medium.2c | 2 cores, 16 GB | 1,600 | 10,000 | 128 |
pg.x2.large.2c | 4 cores, 8 GB | 800 | 20,000 | 192 |
pg.x4.large.2c | 4 cores, 16 GB | 1,600 | 20,000 | 192 |
pg.x8.large.2c | 4 cores, 32 GB | 3,200 | 20,000 | 192 |
pg.x2.xlarge.2c | 8 cores, 16 GB | 1,600 | 25,000 | 256 |
pg.x4.xlarge.2c | 8 cores, 32 GB | 3,200 | 25,000 | 256 |
pg.x8.xlarge.2c | 8 cores, 64 GB | 6,400 | 25,000 | 256 |
pg.x2.3large.2c | 12 cores, 24 GB | 2,400 | 30,000 | 320 |
pg.x4.3large.2c | 12 cores, 48 GB | 4,800 | 30,000 | 320 |
pg.x8.3large.2c | 12 cores, 96 GB | 9,600 | 30,000 | 320 |
pg.x2.2xlarge.2c | 16 cores, 32 GB | 3,200 | 40,000 | 384 |
pg.x4.2xlarge.2c | 16 cores, 64 GB | 6,400 | 40,000 | 384 |
pg.x8.2xlarge.2c | 16 cores, 128 GB | 12,800 | 40,000 | 384 |
pg.x2.3xlarge.2c | 24 cores, 48 GB | 4,800 | 50,000 | 512 |
pg.x4.3xlarge.2c | 24 cores, 96 GB | 9,600 | 50,000 | 512 |
pg.x8.3xlarge.2c | 24 cores, 192 GB | 19,200 | 50,000 | 512 |
pg.x2.4xlarge.2c | 32 cores, 64 GB | 6,400 | 60,000 | 640 |
pg.x4.4xlarge.2c | 32 cores, 128 GB | 12,800 | 60,000 | 640 |
pg.x8.4xlarge.2c | 32 cores, 256 GB | 25,600 | 60,000 | 640 |
pg.x2.13large.2c | 52 cores, 96 GB | 9,600 | 100,000 | 1024 |
pg.x4.13large.2c | 52 cores, 192 GB | 19,200 | 100,000 | 1024 |
pg.x8.13large.2c | 52 cores, 384 GB | 38,400 | 100,000 | 1024 |
pg.x2.8xlarge.2c | 64 cores, 128 GB | 12,800 | 120,000 | 1280 |
pg.x4.8xlarge.2c | 64 cores, 256 GB | 25,600 | 120,000 | 1280 |
pg.x8.8xlarge.2c | 64 cores, 512 GB | 51,200 | 120,000 | 1280 |
pg.x2.13xlarge.2c | 104 cores, 192 GB | 19,200 | 200,000 | 2048 |
pg.x4.13xlarge.2c | 104 cores, 384 GB | 38,400 | 200,000 | 2048 |
pg.x8.13xlarge.2c | 104 cores, 768 GB | 76,800 | 200,000 | 2048 |
Intel SGX-based security-enhanced instance type
ApsaraDB RDS for PostgreSQL provides the fully encrypted database (hardware-enhanced edition) feature. If you enable this feature, you can encrypt sensitive data columns in tables in a database on your ApsaraDB RDS for PostgreSQL instance. Data in the sensitive data columns is transmitted, computed, and stored in ciphertext. The feature provides you with TEE-based data protection based on security-enhanced instance types. TEE is short for trusted execution environment. For more information about how to use the feature, see Overview of the fully encrypted database feature.
Note The following table describes the regions in which Intel SGX-based security-enhanced instance types are available for purchase.
Region | Zone |
China (Hangzhou) | Hangzhou Zone K |
China (Shanghai) | Shanghai Zone B and Shanghai Zone L |
China (Beijing) | Beijing Zone I and Beijing Zone K |
China (Hong Kong) | Hong Kong Zone B and Hong Kong Zone D |
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Encrypted memory | Maximum number of connections | Maximum IOPS | Storage capacity |
RDS High-availability Edition | Intel SGX-based security-enhanced instance type | pg.x4t.medium.2c | 2 cores, 8 GB | 4 GB | 400 | For more information, see Primary ApsaraDB RDS instance types. | PL1 ESSD: 20 GB to 32,000 GB PL2 ESSD: 500 GB to 32,000 GB PL3 ESSD: 1,500 GB to 32,000 GB
|
pg.x4t.large.2c | 4 cores, 16 GB | 8 GB | 800 |
pg.x4t.xlarge.2c | 8 cores, 32 GB | 16 GB | 1,600 |
pg.x4t.2xlarge.2c | 16 cores, 64 GB | 32 GB | 3,200 |
pg.x4t.4xlarge.2c | 32 cores, 128 GB | 64 GB | 6,400 |
Instance types for the economy product type (original ARM architecture)
If you want to purchase an instance type that is supported for the economy product type for your RDS instance, the instance must meet the following requirements:
The RDS instance runs PostgreSQL 13, PostgreSQL 14, or PostgreSQL 15.
The RDS instance uses PL1 ESSDs, PL2 ESSDs, or PL3 ESSDs.
The RDS instance resides in one of the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
Note Instance types for the economy product type are available in a few regions and will be available in other regions and zones in phases. For more information about the regions, visit the ApsaraDB RDS buy page.
Usage notes
Instance types for the economy product type are not supported for RDS instances for which Babelfish is enabled. For more information, see Introduction to Babelfish.
You can change the instance type of an RDS instance from an instance type for the standard product type to an instance type for the economy product type. For more information, see Change instance specifications.
Instance types
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
RDS High-availability Edition | General-purpose instance family | pg.n4m.2c.2m | 2 cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. For more information, see Primary ApsaraDB RDS instance types. | PL1 ESSD: 20 GB to 32,000 GB PL2 ESSD: 500 GB to 32,000 GB PL3 ESSD: 1,500 GB to 32,000 GB
|
pg.n4m.4c.2m | 4 cores, 16 GB | 1600 |
pg.n4m.8c.2m | 8 cores, 32 GB | 3200 |
pg.n2m.2c.2m | 2 cores, 4 GB | 400 |
pg.n2m.4c.2m | 4 cores, 8 GB | 800 |
pg.n2m.8c.2m | 8 cores, 16 GB | 1600 |
Dedicated instance family | pg.x2m.medium.2c | 2 cores, 4 GB | 400 | 20000 | 192 |
pg.x4m.medium.2c | 2 cores, 8 GB | 800 | 20000 | 192 |
pg.x8m.medium.2c | 2 cores, 16 GB | 1600 | 20000 | |
pg.x2m.large.2c | 4 cores, 8 GB | 800 | 40000 | 256 |
pg.x4m.large.2c | 4 cores, 16 GB | 1600 | 40000 | 256 |
pg.x8m.large.2c | 4 cores, 32 GB | 3200 | 40000 | 256 |
pg.x2m.xlarge.2c | 8 cores, 16 GB | 1600 | 50000 | 384 |
pg.x4m.xlarge.2c | 8 cores, 32 GB | 3200 | 50000 | 384 |
pg.x8m.xlarge.2c | 8 cores, 64 GB | 6400 | 50000 | 384 |
pg.x2m.2xlarge.2c | 16 cores, 32 GB | 3200 | 80000 | 640 |
pg.x4m.2xlarge.2c | 16 cores, 64 GB | 6400 | 80000 | 640 |
pg.x8m.2xlarge.2c | 16 cores, 128 GB | 12800 | 80000 | 640 |
pg.x2m.4xlarge.2c | 32 cores, 64 GB | 6400 | 125000 | 1024 |
pg.x4m.4xlarge.2c | 32 cores, 128 GB | 12800 | 125000 | 1024 |
pg.x8m.4xlarge.2c | 32 cores, 256 GB | 25600 | 125000 | 1024 |
pg.x2m.8xlarge.2c | 64 cores, 128 GB | 12800 | 240000 | 2048 |
pg.x4m.8xlarge.2c | 64 cores, 256 GB | 25600 | 240000 | 2048 |
pg.x8m.8xlarge.2c | 64 cores, 512 GB | 51200 | 240000 | 2048 |
Phased-out instance types
The following table describes the phased-out instance types of ApsaraDB RDS for PostgreSQL. The phased-out instance types are no longer available to new RDS instances. We recommend that you select available instance types for new RDS instances.
Phase-out instance types
Instance type | Number of CPU cores | Memory capacity | Maximum number of connections | Maximum IOPS |
rds.pg.t1.small | 1 | 1 GB | 100 | 600 |
pg.x8.4xlarge.2 | 32 | 256 GB | 20,000 | 50,000 |
pg.n1.micro.1 | 1 | 1 GB | 100 | For more information, see Primary ApsaraDB RDS instance types. |
pg.gn5i-c2g1.large.1 | 2 | 8 GB | 800 |
pg.gn5i-c4g1.xlarge.1 | 4 | 16 GB | 1,600 |
pg.gn5i-c8g1.2xlarge.1 | 8 | 32 GB | 3,200 |
pg.gn5i-c16g1.4xlarge.1 | 16 | 64 GB | 6,400 |
pg.gn5i-c16g1.8xlarge.1 | 32 | 128 GB | 12,800 |
pg.gn5i-c28g1.14xlarge.1 | 56 | 224 GB | 22,000 |
pg.n2.small.2c | 1 | 2 GB | 200 |
pg.n2.medium.2c | 2 | 4 GB | 400 |
rds.pg.s1.small | 1 | 2 GB | 200 |
pg.n2.small.1 | 1 | 2 GB | 200 |
pg.n4.8xlarge.1 | 64 | 256 GB | 22,000 |
pg.n8.8xlarge.1 | 64 | 512 GB | 48,000 |
rds.pg.s2.large | 2 | 4 GB | Unlimited | For more information, see Primary ApsaraDB RDS instance types. |
rds.pg.s3.large | 4 | 8 GB |
rds.pg.c1.large | 8 | 16 GB |
rds.pg.c1.xlarge | 8 | 32 GB |
rds.pg.c2.xlarge | 16 | 64 GB |
rds.pg.c2.2xlarge | 16 | 128 GB |
pg.x8.medium.2 | 2 | 16 GB | 2,500 | 4,500 |
pg.x8.large.2 | 4 | 32 GB | 5,000 | 9,000 |
pg.x8.xlarge.2 | 8 | 64 GB | 10,000 | 18,000 |
pg.x8.2xlarge.2 | 16 | 128 GB | 20,000 | 36,000 |
rds.pg.st.h43 | 60 | 470 GB | 12,000 | 50,000 |
pg.n2.medium.1 | 2 | 4 GB | 400 | For more information, see Primary ApsaraDB RDS instance types. |
pg.n4.medium.1 | 2 | 8 GB | 800 |
pg.n2.large.1 | 4 | 8 GB | 800 |
pg.n4.large.1 | 4 | 16 GB | 1,600 |
pg.n2.xlarge.1 | 8 | 16 GB | 1,600 |
pg.n4.xlarge.1 | 8 | 32 GB | 3,200 |
pg.n2.2xlarge.1 | 16 | 32 GB | 3,200 |
pg.n4.2xlarge.1 | 16 | 64 GB | 6,400 |
pg.n8.2xlarge.1 | 16 | 128 GB | 10,000 |
pg.n4.4xlarge.1 | 32 | 128 GB | 12,800 |
pg.n8.4xlarge.1 | 32 | 256 GB | 20,000 |