| 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.
|
| 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.
|
| 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.
|
| 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.
|