Checks whether the specifications of each Elastic Compute Service (ECS) instance match the specified range.
Scenarios
You can specify instance types for ECS instances based on your business requirements. This helps you save costs and prevent excessive fees generated by ECS instances with specifications higher than what you need. This also prevents business interruption caused by insufficient resources on ECS instances.
Risk level
Default risk level: low.
You can change the risk level as required when you apply this rule.
Compliance evaluation logic
- If the specifications of each ECS instance match the specified range, the evaluation result is compliant.
- If the specifications of an ECS instance do not match the specified range, 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-desired-instance-type |
| Rule ID | ecs-desired-instance-type |
| Tag | ECS |
| Automatic remediation | Not supported |
| Trigger type | Configuration change |
| Supported resource type | ECS instance |
| Input parameter | instanceTypesNote Separate the names of multiple instance types with commas (,). |
Non-compliance remediation
For more information about how to modify the specifications of an ECS instance, see Limitations and pre-checks for changing instance types.