Background, scenarios, and rules for high availability architecture best practices-Cloud Config(CloudConfig)-阿里云帮助中心

This topic describes the background, scenarios, and default rules for high-availability architecture best practices.

Background

A multi-zone architecture is an important method for achieving high business availability. In Alibaba Cloud, zones are physically isolated and independent of each other. A multi-zone architecture improves data reliability and enables quick service recovery if the primary zone fails. This compliance package helps you detect cloud resources that do not use a multi-zone architecture.

Scenarios

The best practices for multi-zone architecture are suitable for enterprises with stringent requirements for service continuity and data reliability.

Default rules

Rule name	Rule description
Use multi-zone RDS instances	An RDS instance is considered compliant if it is a multi-zone instance.
Enable zone-redundant storage for OSS buckets	If zone-redundant storage is not enabled, OSS cannot ensure availability and durability if a data center becomes unavailable. This impacts your ability to meet data restoration objectives. An OSS bucket is considered compliant if zone-redundant storage is enabled.
Use multi-zone Redis instances	A Redis instance is considered compliant if it is a multi-zone instance.
Use multi-zone SLB instances	An SLB instance is considered compliant if it is a multi-zone instance.
Use multi-zone ALB instances	An Application Load Balancer (ALB) instance is considered compliant if it is a multi-zone instance. If only one zone is selected, a failure in that zone can cause the ALB instance to fail, which impacts business stability.
Add resources from multiple zones to ALB server groups	An ALB server group is considered compliant if the resources attached to it are distributed across multiple zones. This rule does not apply if no resources are attached to the ALB server group or if the server group is of the IP or Function Compute type.
Associate an Auto Scaling group with at least two vSwitches	An Auto Scaling group is considered compliant if it is associated with at least two vSwitches.
Use multi-zone MongoDB instances	A MongoDB instance is considered compliant if it is a multi-zone instance.
Enable a hot standby cluster for a PolarDB cluster	A PolarDB cluster is considered compliant if a hot standby storage cluster is enabled and data is distributed across multiple zones.
Configure multiple zones for an endpoint service	An endpoint service is considered compliant if it is configured with multiple zones.
Use multi-zone SLB instances and configure resources from multiple zones for server groups	An SLB instance is considered compliant if it is a multi-zone instance and resources from multiple zones are added to all server groups used by its listeners.
Use multi-zone Elasticsearch instances	An Elasticsearch instance is considered compliant if it is a multi-zone instance.
Use regional multi-zone ACK clusters	A regional ACK cluster is considered compliant if its nodes are distributed across three or more zones.
Use a high-availability edition of MSE registry and configuration center	An MSE registry and configuration center is considered compliant if it is a Professional or Serverless edition with nodes deployed across multiple zones.
Deploy MSE cloud-native gateways in multiple zones	An MSE cloud-native gateway is considered compliant if it is deployed across multiple zones.
Use a Bastionhost version that supports multi-zone deployment	A Bastionhost instance is considered compliant if it is an Enterprise Dual-engine or SM-compliant edition. These editions support multi-zone deployment to ensure stability. This rule does not apply to earlier versions.
Use a multi-zone VPN Gateway	A VPN Gateway is considered compliant if it is configured with two vSwitches to ensure cross-zone high availability.
Configure multiple zones for a Transit Router VPC connection	A Transit Router VPC connection is considered compliant if it is configured with two vSwitches in different zones to ensure cross-zone high availability.
Use multi-zone Network Load Balancer instances	A Network Load Balancer (NLB) instance is considered compliant if it is a multi-zone instance.
Use multi-zone cloud-native data warehouse AnalyticDB instances	A cloud-native data warehouse AnalyticDB instance is considered compliant if it is a multi-zone instance.
Use multi-zone Lindorm instances	A Lindorm instance is considered compliant if it is a multi-zone instance.
Use multi-zone HBase clusters	An HBase cluster is considered compliant if it is a multi-zone cluster.
Use zone-redundant Tablestore instances	A Tablestore instance is considered compliant if it uses zone-redundant storage.
Associate Container Registry instances with zone-redundant OSS buckets	A Container Registry instance is considered compliant if it is associated with a zone-redundant OSS bucket.
Use multi-zone KMS instances	A KMS instance is considered compliant if it is a multi-zone instance.
Use multi-zone Message Queue for Apache RocketMQ 5.0 instances	A Message Queue for Apache RocketMQ 5.0 instance is considered compliant if it is a multi-zone instance.
Use multi-zone Flink instances	A Flink instance is considered compliant if it is a multi-zone instance.
Use multi-zone Gateway Load Balancer instances	A Gateway Load Balancer (GWLB) instance is considered compliant if it is a multi-zone instance.
Establish connections for both the active and standby tunnels of a dual-tunnel VPN gateway	A dual-tunnel VPN gateway is considered compliant if both its active and standby tunnels have established connections with the peer.
Use regional multi-zone ACS clusters	A regional ACS cluster is considered compliant if its nodes are distributed across three or more zones.
Use zone-redundant Log Service projects	A Log Service project is considered compliant if it uses zone-redundant storage.
Use multi-zone gateway instances	A gateway instance is considered compliant if it is a multi-zone instance.
Use multi-zone Message Queue for Apache Kafka instances	A Message Queue for Apache Kafka instance is considered compliant if it is a multi-zone instance.
Use multi-zone PolarDB-X 2.0 instances	A PolarDB-X 2.0 instance is considered compliant if it uses a multi-zone architecture.
Add resources from multiple zones to Network Load Balancer server groups	An NLB server group is considered compliant if the resources it contains are distributed across multiple zones. This rule does not apply if the server group contains no resources or if the resource type is IP.
Use multi-zone ApsaraDB for ClickHouse cluster instances	An ApsaraDB for ClickHouse cluster instance is considered compliant if it is a multi-zone instance. This rule applies only to Community Edition clusters.
Use a multi-zone disaster recovery architecture for MaxCompute projects	A MaxCompute project is considered compliant if it uses a multi-zone disaster recovery architecture.
Configure multiple origin servers for a CDN accelerated domain name	A CDN accelerated domain name is considered compliant if multiple origin servers are configured.
Configure multiple origin servers for a DCDN accelerated domain name	A DCDN accelerated domain name is considered compliant if multiple origin servers are configured.
Use zone-redundant ESSD data disks	An ESSD data disk is considered compliant if it is a zone-redundant disk. This rule does not apply to system disks.
Use Express Connect in high-availability mode	An Express Connect circuit is considered compliant if it is used in high-availability mode. This mode requires you to request two access points for the circuit in the same region.