Evaluates whether each subscription PolarDB cluster has more than a specified number of days remaining before expiration. If so, the cluster is evaluated as Compliant.
Scenarios
Use this rule to ensure subscription PolarDB clusters are renewed before expiration, preventing business interruptions caused by expired clusters.
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 PolarDB cluster has more than a specified number of days remaining before expiration, the evaluation result is Compliant.
- If a subscription PolarDB cluster has fewer than or exactly a specified number of days remaining before expiration, the evaluation result is Incompliant. For more information about how to remediate an incompliant configuration, see Incompliance remediation.
Rule details
| Item | Description |
| Rule name | polardb-cluster-expired-check |
| Rule identifier | polardb-cluster-expired-check |
| Tag | PolarDB and ResourceExpired |
| Automatic remediation | Not supported |
| Trigger type | Configuration change and periodic execution |
| Evaluation frequency | Every 24 hours |
| Supported resource type | PolarDB cluster |
| Input parameter | days. Default value: 30. Unit: days. |
Incompliance remediation
Renew a subscription PolarDB cluster before it expires. For more information, see Manual renewal.