Evaluates whether each subscription ApsaraDB for Redis instance has more than a specified number of days remaining before expiration. If so, the instance is evaluated as Compliant.
Scenarios
Ensure that you renew each subscription ApsaraDB for Redis instance before it expires to avoid service disruptions.
Risk level
Default risk level: high.
You can change the risk level based on your business requirements when you apply this rule.
Compliance evaluation logic
- If a subscription ApsaraDB for Redis instance has more than a specified number of days remaining before expiration, the instance is evaluated as Compliant.
- If a subscription ApsaraDB for Redis instance has fewer than or exactly a specified number of days remaining before expiration, the instance is evaluated as Incompliant. For more information about how to remediate an incompliant configuration, see Incompliance remediation.
Rule details
| Item | Description |
| Rule name | redis-instance-expired-check |
| Rule identifier | redis-instance-expired-check |
| Tag | Redis and ResourceExpired |
| Automatic remediation | Not supported |
| Trigger type | Configuration change and periodic execution |
| Evaluation frequency | Every 24 hours |
| Supported resource type | ApsaraDB for Redis instance |
| Input parameter | days. Default value: 30. Unit: days. |
Incompliance remediation
Renew subscription ApsaraDB for Redis instances before they expire, or enable auto-renewal. For more information, see Instance renewal.