Checks whether the running duration of each pay-as-you-go Elastic Compute Service (ECS) instance is less than or equal to the specified value. If so, the evaluation result is Compliant. This rule does not apply to subscription ECS instances.
Scenarios
After a pay-as-you-go ECS instance is created, you can change the billing method of the ECS instance to subscription based on the running duration of the ECS instance. This is more cost-effective and allows you to reserve resources for later use.
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 ECS instance is less than or equal to the specified value. If so, the evaluation result is Compliant.
This rule does not apply to subscription ECS instances.
Rule details
Parameter | Description |
Rule Template Name | ecs-long-time-post-paid-check |
Rule Template Identifier | |
Tag | ECS |
Automatic remediation | Not supported |
Invoke Type | Configuration Change |
Supported resource type | ECS instance (ACS::ECS::Instance) |
Input parameter | The parameter name is runTime. Default value: 30. Unit: days. The parameter specifies the duration during which the ECS instance runs. Maximum value: 365. |
Incompliance remediation
If the duration during which the pay-as-you-go ECS instance runs is greater than 365 days, we recommend that you change the billing method of the ECS instance to subscription. For more information, see Change the billing method of an instance from pay-as-you-go to subscription.