Elastic Compute Service
Applicable scenarios | Description |
Applicable scenarios | Description |
Regular compliance check | Applicable to scenarios such as baseline compliance verification and post-installation patch status validation. It performs routine, automated patch scanning and compliance checks on ECS instances, only verifying patch installation status, identifying vulnerabilities and compliance risks, and generating compliance reports, without installing patches. |
Temporary emergency fixing | Applicable to urgent scenarios, such as outbreaks of high-risk vulnerabilities and emergency responses to security incidents. If an ECS instance is affected by high-risk vulnerabilities, or subject to security announcements or emergency compliance requirements, you can scan the target instance immediately and install patches to mitigate security risks as quickly as possible, ensuring stable and secure service operation. |
Concept | Description |
Concept | Description |
Patch baseline | A patch baseline is a collection of patch rules used as the standard for patch operations and compliance judgments. The system automatically approves or rejects patch installations based on this baseline. |
Operating system type | Operating system version |
Operating system type | Operating system version |
Ubuntu |
|
Debian |
|
Step | Description |
Step | Description |
|
|
Create a patch scanning plan to check patch status and troubleshoot issues on target instances, and identify non-compliant items, vulnerabilities, and exceptions in advance. | |
Check the patch scanning compliance of target instances, including compliance status, number of non-compliant patches, details of missing patches, and risk alerts. These reports support patch fixing and compliance improvement. | |
| For non-compliant instances, create a scan-and-install patch plan to check and install patches in one step for efficient compliance improvement. |
Step | Description |
Step | Description |
|
|
The system first checks patch status, and then installs patches for detected issues to complete emergency fixing in one step. | |
| Check the patch installation compliance of target instances, including compliance status, number of non-compliant patches, details of missing patches, and risk alerts. These reports support subsequent patch fixing and compliance improvement. tip Based on compliance reports, you can choose whether to scan for and install patches again. If needed, perform the operations by following the three steps in this table. |