Updated on 2023-12-28 GMT+08:00

Basic Concepts

DB Instances

The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance runs a DB engine. For details about DB instance types, specifications, engines, versions, and statuses, see DB Instance Description.

DB Engines

RDS supports the following DB engines:

  • MySQL
  • PostgreSQL
  • MariaDB

For details about the supported versions, see DB Engines and Versions.

DB Instance Types

There are two types of RDS DB instances: single and primary/standby. Different series support different DB engines and instance specifications.

For details about DB instance types, see DB Instance Introduction and Function Comparison.

DB Instance Classes

The DB instance class determines the compute (vCPUs) and memory capacity (memory size) of a DB instance. For details, see DB Instance Classes.

Automated Backups

When you create a DB instance, an automated backup policy is enabled by default, but after the DB instance is created, you can modify the policy if needed. RDS will automatically create full backups for DB instances based on your settings.

Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually.

Regions and AZs

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

  • Regions are defined by their geographical location and network latency. Each region is completely independent, improving fault tolerance and stability. After a resource is created, its region cannot be changed.
  • An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.

Figure 1 shows the relationship between regions and AZs.

Figure 1 Regions and AZs


Projects are used to group and isolate OpenStack resources (compute, storage, and network resources). A project can be a department or a project team. Multiple projects can be created for a single account.