Checks whether the remaining validity period of each subscription Elastic Compute Service (ECS) instance is longer than the period specified by the input parameter.
Scenarios
You cannot use a subscription ECS instance as expected after the subscription expires. To prevent business interruption caused by a subscription ECS instance that is automatically released, you must renew the ECS instance within a specific period. Otherwise, instance resources such as vCPUs, memory, and disks are released and data stored on them is permanently lost.
Risk level
Default risk level: high.
You can change the risk level as required when you apply this rule.
Compliance evaluation logic
- If the remaining validity period of each subscription ECS instance is longer than the period specified by the input parameter, the evaluation result is compliant.
- If the remaining validity period of a subscription ECS instance is shorter than or equal to the period specified by the input parameter, the evaluation result is non-compliant. For more information about how to correct the non-compliant configuration, see Non-compliance remediation.
Rule details
| Item | Description |
|---|---|
| Rule name | ecs-instance-expired-check |
| Rule ID | ecs-instance-expired-check |
| Tag | ECS, Instance, and ResourceExpired |
| Automatic remediation | Not supported |
| Trigger type |
|
| Input parameter | days. Default value: 30. Unit: days.
|
Non-compliance remediation
For more information about how to renew a subscription ECS instance, see Renewal overview.