Evaluates whether the append-only file (AOF) persistence feature is disabled for ApsaraDB for Redis instances. If AOF persistence is disabled, the evaluation result is Compliant.
Scenarios
If you use an ApsaraDB for Redis instance in cache-only scenarios and do not require data persistence, we recommend that you disable AOF persistence to improve instance performance, reduce disk usage, and lower the additional load on the instance.
Risk level
Default risk level: medium.
You can change the risk level when you apply this rule based on your business requirements.
Compliance evaluation logic
-
If AOF persistence is disabled for an ApsaraDB for Redis instance, the evaluation result is Compliant.
-
If AOF persistence is enabled for an ApsaraDB for Redis instance, the evaluation result is Non-compliant.
-
If an ApsaraDB for Redis instance is not a Tair instance, the evaluation result is Not Applicable.
Rule details
|
Item |
Description |
|
Rule name |
redis-instance-tair-type-close-aof |
|
Rule ID |
|
|
Tag |
Redis and Instance |
|
Automatic remediation |
Not supported |
|
Trigger type |
Configuration change |
|
Supported resource type |
ApsaraDB for Redis instance |
|
Input parameter |
None |
Non-compliance remediation
Disable AOF persistence for your ApsaraDB for Redis instances. For more information, see Disable AOF persistence.