Idle ECS Check
Rule Details
Parameter |
Description |
---|---|
Rule Name |
stopped-ecs-date-diff |
Identifier |
Idle ECS Check |
Description |
If an ECS has been stopped for longer than the time allowed, and no operations have been performed on it, this ECS is non-compliant. |
Tag |
ecs |
Trigger Type |
Periodic |
Filter Type |
ecs.cloudservers |
Rule Parameters |
allowDays: The number of days allowed. The value must be a string. |
Application Scenarios
If an ECS is shut down and no operations are performed on it for a long time, the ECS may have security risks because it was not maintained.
If an ECS is no longer needed, you are advised to delete it to save costs. If such ECS has sensitive information, the data may be restored even if the ECS is shut down. Clearing the data before deleting the ECS can reduce security risks.
Solution
Check whether your ECSs are still required. If not, delete the ECSs. For details, see ECS Deletion and Unsubscription.
If the ECSs are still required, start and maintain them periodically.
Rule Logic
- If an ECS instance is not shut down, the ECS instance is compliant.
- If an ECS instance is shut down and the interval since the last operation does not exceed the time allowed, the ECS instance is compliant.
- If an ECS instance is shut down and the interval since the last operation exceeds the time allowed, the ECS instance is non-compliant.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot