The smallest management unit of RDS is DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance can contain multiple user-created databases, and you can access a DB instance using the same tools and applications that you use with a stand-alone DB instance. You can easily create or modify DB instances using the management console or HTTPS-compliant application programming interfaces (APIs). RDS does not have limits on the number of running DB instances. Each DB instance has a unique identifier.
DB instances are classified into the following types.
DB Instance Type | Description | Notes |
|---|---|---|
Single-node | It uses a standalone architecture, which is more cost-effective than mainstream primary/standby instances. | If a fault occurs on a single-node instance, the instance cannot recover in a timely manner. Do not use single-node instances in any production environment. |
Primary/Standby | It uses an HA architecture. The primary and standby instances can be deployed in different AZs. The primary and standby instances share the same IP address. |
|
Read replica | It uses a standalone architecture (without a standby node). |
|
Cluster | The Microsoft Always On architecture. There is one primary node, one standby node, and up to five read-only nodes. It features higher availability, reliability, and scalability. | Only for RDS for SQL Server. |
You can use RDS to create and manage DB instances running various DB engines.
For details about differences and function comparison between different MySQL instance types, see RDS for MySQL.
For details about differences and function comparison between different PostgreSQL instance types, see RDS for PostgreSQL.
For details about differences and function comparison between different SQL Server instance types, see RDS for SQL Server.