What are the background, scenarios, and rules of best practices for high availability architecture - Cloud Config

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

Background

Multi-zone architecture is a crucial strategy for achieving high availability in your business operations. The zones within Alibaba Cloud operate independently, ensuring that one zone's availability does not impact another. A system utilizing multi-zone architecture offers robust data reliability, enabling real-time business recovery in the event of a primary zone failure. This compliance package helps identify Alibaba Cloud resources not employing multi-zone architecture.

Scenarios

This compliance package is ideal for scenarios demanding high service continuity and data reliability.

Default rules

Rule Name	Rule Description
Use Multi-Zone RDS Instances	Verifies that each RDS instance is configured with multi-zone architecture, resulting in a Compliant status.
Enable Zone-Redundant Storage for OSS Buckets	Evaluates OSS buckets to ensure the Zone-Redundant Storage (ZRS) feature is enabled, which is critical for consistent service and data restoration in the event of a data center outage, resulting in a Compliant status.
Use Multi-Zone Redis Instances	Checks if each Redis instance employs multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone SLB Instances	Assesses whether SLB instances are configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone ALB Instances	Verifies that each ALB instance utilizes multi-zone architecture to avoid business disruption in case of a zone failure, resulting in a Compliant status.
Add Resources from Multiple Zones to ALB Server Groups	Checks for multi-zone resource distribution within ALB server groups, resulting in a Compliant status. This rule is not applicable to server groups of the IP or Function Compute type.
Associate at Least Two vSwitches with Scaling Groups	Ensures that each scaling group is associated with at least two vSwitches, resulting in a Compliant status.
Use Multi-Zone MongoDB Instances	Verifies that each ApsaraDB for MongoDB instance is configured with multi-zone architecture, resulting in a Compliant status.
Enable Hot Standby Clusters for PolarDB Clusters	Checks for the activation of the hot standby cluster feature and multi-zone data distribution in each PolarDB cluster, resulting in a Compliant status.
Configure Multiple Zones for Endpoint Services	Ensures that each endpoint service is configured across multiple zones, resulting in a Compliant status.
Use Multi-Zone SLB Instances and Add Resources from Multiple Zones to Server Groups	Checks for multi-zone architecture in SLB instances and multi-zone resource addition to server groups used by all listeners, resulting in a Compliant status.
Use Multi-Zone Elasticsearch Instances	Assesses whether each Elasticsearch instance employs multi-zone architecture, resulting in a Compliant status.
Use Region-Level Multi-Zone ACK Clusters	Verifies the use of region-level ACK clusters with nodes distributed across three or more zones, resulting in a Compliant status.
Use High-Availability Edition MSE Registration Configuration Centers	Checks for the use of Professional or Serverless Edition MSE registration configuration centers deployed across multiple zones, resulting in a Compliant status.
Deploy MSE Cloud-Native Gateways in Multiple Zones	Evaluates whether MSE cloud-native gateways are deployed across different zones, resulting in a Compliant status.
Use Multi-Zone Deployed Bastionhost Editions	Assesses whether Enterprise Dual-engine or SM Edition Bastionhost is deployed across multiple zones for stability, resulting in a Compliant status. Historical editions are Not applicable.
Use Multi-Zone VPN Gateways	Verifies that each VPN Gateway is configured with two vSwitches for high availability across zones, resulting in a Compliant status.
Configure Multiple Zones for TransitRouter VPC Connections	Ensures that each TransitRouter VPC connection is configured with two vSwitches distributed in different zones for high availability, resulting in a Compliant status.
Use Multi-Zone Network Load Balancer Instances	Checks whether network load balancer instances are configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone AnalyticDB for PostgreSQL Instances	Verifies that each AnalyticDB for PostgreSQL instance employs multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone Lindorm Instances	Checks whether each Lindorm instance is configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone HBase Clusters	Assesses whether each HBase cluster utilizes multi-zone architecture, resulting in a Compliant status.
Use Zone-Redundant Tablestore Instances	Verifies that each Tablestore instance employs a zone-redundant architecture, resulting in a Compliant status.
Associate Container Image Instances with Zone-Redundant OSS Buckets	Checks whether each container image instance is linked to zone-redundant OSS buckets, resulting in a Compliant status.
Use Multi-Zone KMS Instances	Ensures that each KMS instance is configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone RocketMQ 5.0 Instances	Checks whether each RocketMQ 5.0 instance uses multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone Flink Instances	Verifies that each Flink instance is configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone Gateway Load Balancer Instances	Assesses whether each Gateway Load Balancer instance employs multi-zone architecture, resulting in a Compliant status.
Establish Connections for Both Primary and Secondary Tunnels of Dual-Tunnel VPN Gateways	Checks for established connections in both the primary and secondary tunnels of dual-tunnel VPN Gateways, resulting in a Compliant status.
Use Region-Level Multi-Zone ACS Clusters	Ensures the use of region-level ACS clusters with nodes distributed across three or more zones, resulting in a Compliant status.
Use Zone-Redundant Log Service Projects	Checks whether each Log Service project employs a zone-redundant architecture, resulting in a Compliant status.
Use Multi-Zone API Gateway Instances	Verifies that each API Gateway instance utilizes multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone Kafka Instances	Assesses whether each Kafka instance is configured with multi-zone architecture, resulting in a Compliant status.
Use Multi-Zone PolarDB-X 2.0 Instances	Checks for multi-zone architecture in each PolarDB-X 2.0 instance, resulting in a Compliant status.
Add Resources from Multiple Zones to Network Load Balancer Server Groups	Verifies that resources within server groups of each network load balancer instance are distributed across multiple zones, resulting in a Compliant status. If no resources are added to the server group or the resource type is IP, the evaluation is Not applicable.
Use Multi-Zone ClickHouse Cluster Instances	Checks whether each ClickHouse cluster instance employs multi-zone architecture, resulting in a Compliant status. Note that only the Community Edition is included.
Use Zone-Disaster Recovery Architecture for MaxCompute Projects	Ensures that each MaxCompute project is configured with a zone-disaster recovery architecture, resulting in a Compliant status.
Configure Multiple Origin Servers for CDN Domain Names	Checks for the configuration of multiple origin servers for each CDN domain name, resulting in a Compliant status.
Configure Multiple Origin Servers for DCDN Domain Names	Verifies the configuration of multiple origin servers for each DCDN domain name, resulting in a Compliant status.
Use Zone-Redundant ESSD Data Disks	Checks whether each ESSD data disk is configured with zone-redundant architecture, resulting in a Compliant status. System disks are considered Not applicable.
Use High-Reliability Mode Express Connect Circuits	Ensures that each Express Connect circuit is in high-reliability mode with two access points requested for the same region, resulting in a Compliant status.