Does TaurusDB for PostgreSQL Support Cross-AZ High Availability?

Yes. When you buy a DB instance, you can select Primary/Standby for DB Instance Type and then select different AZs for Primary AZ and Standby AZ.

TaurusDB for PostgreSQL does not support 3-AZ deployment.

An AZ is a physical region where resources have independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. You can deploy your instance across AZs in some regions.

For example, if your VPC subnet is deployed in AZ 3, you can select AZ 1 and AZ 2 that are in the same region as AZ 3 when buying a primary/standby instance. The three AZs can communicate with each other.

TaurusDB for PostgreSQL allows you to deploy primary/standby instances in an AZ or across AZs. You can determine whether the standby AZ is the same as the primary AZ.

• If they are different (default setting), the primary and standby instances are deployed in different AZs to ensure failover support and high availability.
• If they are the same, the primary and standby instances are deployed in the same AZ. If an AZ failure occurs, high availability cannot be ensured.