Evaluates whether each subscription ApsaraDB RDS instance has more than a specified number of days remaining before expiration. If so, the result is Compliant.
Scenarios
A subscription ApsaraDB RDS instance becomes unavailable after the subscription expires. Use this rule to verify that each instance is renewed before the subscription ends, preventing business interruptions.
Risk level
Default risk level: high.
You can change the risk level when you apply this rule.
Compliance evaluation logic
- If the subscription ApsaraDB RDS instance has more than the specified number of days remaining before expiration, the evaluation result is Compliant.
- If the subscription ApsaraDB RDS instance has fewer than or exactly the specified number of days remaining before expiration, the evaluation result is Incompliant. For more information, see Incompliance remediation.
Rule details
| Item | Description |
| Rule name | rds-instance-expired-check |
| Rule identifier | rds-instance-expired-check |
| Tag | RDS and ResourceExpired |
| Automatic remediation | Not supported |
| Trigger type | Configuration change and periodic execution |
| Evaluation frequency | Interval of 24 hours |
| Supported resource type | ApsaraDB RDS instance |
| Input parameter | days. Default value: 30. Unit: days.Note Separate multiple values with commas (,). |
Incompliance remediation
Renew an ApsaraDB RDS instance. For more information, see Manual renewal.