If the running duration of a pay-as-you-go ApsaraDB RDS instance is less than or equal to the specified value, the evaluation result is Compliant. This rule does not apply to subscription ApsaraDB RDS instances.
Scenarios
After a pay-as-you-go ApsaraDB RDS instance is created, you can change its billing method to subscription based on the running duration. This is more cost-effective and allows you to reserve resources in advance.
Risk level
Default risk level: low.
When you apply this rule, you can change the risk level based on your business requirements.
Compliance evaluation logic
-
Checks whether the running duration of each pay-as-you-go ApsaraDB RDS instance is less than or equal to the specified value. If so, the evaluation result is Compliant.
-
This rule does not apply to subscription ApsaraDB RDS instances.
Rule details
|
Parameter |
Description |
|
Rule Template Name |
rds-long-time-post-paid-check |
|
Rule Template Identifier |
|
|
Tag |
ApsaraDB RDS |
|
Automatic remediation |
Not supported |
|
Invoke Type |
Configuration Change |
|
Supported resource type |
ApsaraDB RDS instance (ACS::RDS::DBInstance) |
|
Input parameter |
The parameter name is runTime. Default value: 30. Unit: days. Specifies the running duration of an ApsaraDB RDS instance. Maximum value: 365. |
Non-compliance remediation
If the running duration of a pay-as-you-go ApsaraDB RDS instance exceeds 365 days, we recommend that you change the billing method to subscription. For more information, see ModifyDBInstancePayType.