The best practices for sending resource expiration reminders help you check the stability of cloud resources from the perspective of resource expiration risks. This helps identify potential risks in advance and improve stability and O&M efficiency. This topic describes the default rules in the best practices for sending resource expiration reminders.
Rule name | Description |
Checks whether the duration between the expiration date of each AnalyticDB for MySQL cluster (Data Warehouse Edition) and the current date is greater than a specified period of time. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for an instance, the evaluation result is also Compliant. This rule applies only to subscription resource instances and does not apply to pay-as-you-go resource instances. | |
Checks whether the duration between the expiration date of each bastion host and the current date is greater than a specified period of time. If so, the evaluation result is Compliant. Default value: 30. Unit: days. | |
Checks whether the duration between the expiration date of each EIP bandwidth plan and the current date is greater than a specified period of time. If so, the evaluation result is Compliant. Default value: 30. Unit: days. This rule applies only to subscription resource instances and does not apply to pay-as-you-go resource instances. | |
Checks whether the duration between the expiration date of each CEN bandwidth plan and the current date is greater than a specified period of time. If so, the evaluation result is Compliant. Default value: 30. Unit: days. | |
Checks whether the validity period of a CloudSSO SAML signature certificate exceeds the specified number of days. If no, the evaluation result is Incompliant. Default value: 90. Unit: days. | |
Checks whether the validity period of a CloudSSO SCIM key exceeds the specified number of days. If no, the evaluation result is Incompliant. Default value: 90. Unit: days. | |
Checks whether the duration between the last update date of each image version in a Container Registry repository and the current date is less than a specified number of days. If so, the evaluation result is Compliant. Default value: 180. Unit: days. | |
Checks whether the duration between the expiration date of each Anti-DDoS instance and the current date is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. | |
If you use subscription resources, you must renew the resources before they expire. This prevents your instances from being stopped due to expired resources. Checks whether the duration between the expiration date and the check date of each subscription resource is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for an instance, the evaluation result is also Compliant. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
If the duration between the creation date of the image of each ECS instance and the current date is less than a specified number of days, the evaluation result is Compliant. Default value: 180. Unit: days. | |
Checks whether the duration between the expiration date of each EIP and the current date is greater than a specified period of time. If so, the evaluation result is Compliant. Default value: 30. Unit: days. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
Checks whether the duration between the expiration date and the check date of each subscription ApsaraDB for HBase cluster is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. | |
Checks whether the duration between the expiration date and the check date of each subscription ApsaraDB for MongoDB cluster is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for a cluster, the evaluation result is also Compliant. | |
If you use subscription resources, you must renew the resources before they expire. This prevents your instances from being stopped due to expired resources. Checks whether the duration between the expiration date and the check date of each subscription resource is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for an instance, the evaluation result is also Compliant. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
Checks whether the duration between the expiration date of each PolarDB for Xscale 1.0 instance and the current date is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. This rule applies only to subscription resource instances and does not apply to pay-as-you-go resource instances. | |
Checks whether the duration between the expiration date of each PolarDB for Xscale 2.0 instance and the current date is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. This rule applies only to subscription resource instances and does not apply to pay-as-you-go resource instances. | |
Checks whether the time when the AccessKey pair of each RAM user was created is earlier than the specified number of days before the check time. If so, the evaluation result is Compliant. Default value: 90. Unit: days. | |
Checks whether the time when the AccessKey pair of each RAM user was used is earlier than the specified number of days before the current day. If so, the evaluation result is Compliant. Default value: 90. Unit: days. | |
Checks whether each RAM user has logged on within the last 90 days. If so, the evaluation result is Compliant. If a RAM user has been updated within the last 90 days, the evaluation result is Compliant regardless of whether the RAM user has recently logged on. For RAM users that have no console access, the evaluation result is Not Applicable. | |
If you use subscription resources, you must renew the resources before they expire. This prevents your instances from being stopped due to expired resources. Checks whether the duration between the expiration date and the check date of each subscription resource is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
Checks whether the duration between the expiration date and the check date of each subscription ApsaraDB for Redis instance is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for an instance, the evaluation result is also Compliant. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
If you use subscription resources, you must renew the resources before they expire. This prevents your instances from being stopped due to expired resources. Checks whether the duration between the expiration date and the check date of each subscription resource is greater than a specified number of days. If so, the evaluation result is Compliant. Default value: 30. Unit: days. If auto-renewal is enabled for an instance, the evaluation result is also Compliant. For pay-as-you-go resources, the evaluation result is Not Applicable. | |
Checks whether the duration between the expiration date of the SLB certificate and the current date is greater than the specified value. If so, the evaluation result is Compliant. Default value: 90. Unit: days. |