Cloud Config provides built-in compliance rules to verify that backup is enabled for cloud products such as Tair (Redis OSS-compatible), PolarDB, and ApsaraDB RDS. Use these rules to detect and remediate disabled backups. The following table lists the default rules.
|
Rule name |
Rule description |
|
An ECI container group with a mounted volume is considered compliant. |
|
|
An RDS instance with log backup enabled is considered compliant. |
|
|
An ADB cluster with log backup enabled is considered compliant. |
|
|
Meet the specified retention period for level-2 backups of a PolarDB cluster |
A PolarDB cluster is compliant if its level-2 backup retention period is greater than or equal to the specified number of days. The default value is 30 days. The cluster is non-compliant if level-2 backup is disabled or the retention period is less than the specified number of days. |
|
Meet the specified retention period for log backups of a PolarDB cluster |
A PolarDB cluster is compliant if its log backup retention period is greater than or equal to the specified number of days. The default value is 30 days. The cluster is non-compliant if log backup is disabled or the retention period is less than the specified number of days. |
|
A Redis instance with incremental backup enabled is considered compliant. This rule applies only to Tair instances and does not apply to other instance types. |
|
|
Without versioning, you cannot recover overwritten or deleted data. An OSS bucket is considered compliant if versioning is enabled. |
|
|
A MongoDB instance with log backup enabled is considered compliant. |
|
|
A NAS file system with a backup plan is considered compliant. |
|
|
An OceanBase cluster with database backup enabled is considered compliant. |