Help Center/ Config/ User Guide/ Resource Compliance/ Built-In Policies/ GaussDB/ Cross-AZ Deployment Check
Updated on 2025-08-25 GMT+08:00
View PDF
Share

Cross-AZ Deployment Check

Rule Details

Table 1 Rule details

Parameter

Description

Rule Name

gaussdb-instance-multiple-az-check

Identifier

gaussdb-instance-no-public-ip-check

Description

If a GaussDB instance is deployed in an AZ, this instance is non-compliant.

Tag

gaussdb

Trigger Type

Configuration change

Filter Type

gaussdb.instance

Rule Parameters

None

Application Scenarios

An AZ is a physical location that uses independent power supply and networks. AZs in the same region can communicate with each other over an intranet. Multi-AZ deployment of databases is the key to high availability (HA) and disaster recovery (DR).

In extreme cases (for example, an entire AZ is unavailable due to natural disasters), you can promote the DR instance to primary to prevent data loss and avoid service interruption.

Solution

When buying a GaussDB instance, select multiple AZs.

Rule Logic

  • If a GaussDB instance is deployed in an AZ, this instance is non-compliant.
  • If a GaussDB instance is deployed across AZs, this instance is compliant.
Parent topic: GaussDB