Help Center/ Config/ User Guide/ Resource Compliance/ Built-In Policies/ Distributed Cache Service/ 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

dcs-redis-high-tolerance

Identifier

Cross-AZ Deployment Check

Description

If a DCS for Redis instance is not an HA DB instance (deployed in a single AZ), this instance is non-compliant.

Tag

dcs

Trigger Type

Configuration change

Filter Type

dcs.redis

Rule Parameters

None

Application Scenarios

You can deploy primary/standby instances in a single AZ or across AZs. For cross-AZ deployment, DCS initiates and maintains data synchronization for your Redis instances. High availability is achieved by having a standby instance take over in the event that a failure occurs on the master node. When operations are read-heavy, you can use DCS Redis 4.0 or later instances that support read/write splitting, or cluster instances that have multiple replicas. DCS maintains data synchronization between the master and replicas. You can connect to different addresses of an instance to isolate read and write operations. For details, see the Security White Paper.

Solution

By enabling multi-AZ for a single-AZ cluster instance, you can deploy the instance in two AZs for DR. For details, see Changing Cluster DCS Instances to be Across AZs.

Rule Logic

  • If a DCS for Redis instance is deployed in a single AZ, this instance is non-compliant.
  • If a DCS for Redis instance is deployed across AZs, this instance is compliant.