Multi-AZ Deployment Best Practices

The following table describes the compliance rules and solutions in the sample template.

**Table 1** Conformance package description
Rule	Cloud Service	Description
css-cluster-multiple-az-check	css	If a CSS cluster is not deployed across AZs, the cluster is noncompliant.
gaussdb-nosql-deploy-in-single-az	gemini db	If there is a single-AZ GeminiDB instance, this rule is noncompliant.
as-multiple-az	as	If an AS group is deployed in a single AZ, this AS group is noncompliant.
mrs-cluster-multiAZ-deployment	mrs	If an MRS cluster is deployed in a single AZ, this cluster is noncompliant.
rds-instance-multi-az-support	rds	If an RDS instance does not support multi-AZ deployment, this RDS instance is noncompliant.
dcs-redis-high-tolerance	dcs	If a DCS Redis instance does not have cross-AZ deployment enabled, this instance is noncompliant.
elb-multiple-az-check	elb	If a load balancer is mapped to only one AZ, this load balancer is noncompliant. If a load balancer is mapped to fewer than two AZs, this load balancer is noncompliant.
gaussdb-instance-multiple-az-check	gaussdb	If a GaussDB instance does not support cross-AZ deployment, this instance is noncompliant.
gaussdb-mysql-instance-multiple-az-check	taurus db	If a TaurusDB instance does not support cross-AZ deployment, this instance is noncompliant.