AWS inspector: Fixed broken documentation links for Inspector EC2 scanning
Summary
Corrected multiple broken hyperlinks in EC2 scanning documentation.
Security assessment
The changes fix URL formatting errors but don't alter security content or address vulnerabilities.
Evidence
+You can check when an EC2 instance was last scanned for vulnerabilities from the Instances tab on the **Account management** page or by using the [ListCoverage](https://docs.aws.amazon.com/inspector/v2/APIReference/API_ListCoverage.html) command.
Diff
diff --git a/inspector/latest/user/scanning-ec2.md b/inspector/latest/user/scanning-ec2.md index 1f7dd38de..773cb9877 100644 --- a//inspector/latest/user/scanning-ec2.md +++ b//inspector/latest/user/scanning-ec2.md @@ -106 +106 @@ Amazon Inspector updates the **Last scanned** field for an EC2 instance when an -You can check when an EC2 instance was last scanned for vulnerabilities from the Instances tab on the **Account management** page or by using the [ListCoverage](https://docs.aws.amazon.com//inspector/v2/APIReference/API_ListCoverage.html) command. +You can check when an EC2 instance was last scanned for vulnerabilities from the Instances tab on the **Account management** page or by using the [ListCoverage](https://docs.aws.amazon.com/inspector/v2/APIReference/API_ListCoverage.html) command. @@ -110 +110 @@ You can check when an EC2 instance was last scanned for vulnerabilities from the -In order for Amazon Inspector to detect software vulnerabilities for an Amazon EC2 instance using the agent-based scan method, the instance must be a [managed instance](https://docs.aws.amazon.com//systems-manager/latest/userguide/managed_instances.html) in Amazon EC2 Systems Manager (SSM). An SSM managed instance has the SSM Agent installed and running, and SSM has permission to manage the instance. If you are already using SSM to manage your instances, no other steps are needed for agent-based scans. +In order for Amazon Inspector to detect software vulnerabilities for an Amazon EC2 instance using the agent-based scan method, the instance must be a [managed instance](https://docs.aws.amazon.com/systems-manager/latest/userguide/managed_instances.html) in Amazon EC2 Systems Manager (SSM). An SSM managed instance has the SSM Agent installed and running, and SSM has permission to manage the instance. If you are already using SSM to manage your instances, no other steps are needed for agent-based scans. @@ -126 +126 @@ You can also automate SSM management of all your EC2 instances, without the use - 2. Use the AWS CLI to verify that the SSM Agent is running. For more information, see [Checking SSM Agent status and starting the agent](https://docs.aws.amazon.com//systems-manager/latest/userguide/ssm-agent-status-and-restart.html). + 2. Use the AWS CLI to verify that the SSM Agent is running. For more information, see [Checking SSM Agent status and starting the agent](https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-agent-status-and-restart.html). @@ -234 +234 @@ Amazon Inspector updates the **Last scanned** field for an Amazon EC2 instance w -You can check when an EC2 instance was last scanned for vulnerabilities from the Instances tab on the Account management page or by using the [ListCoverage](https://docs.aws.amazon.com//inspector/v2/APIReference/API_ListCoverage.html) command. +You can check when an EC2 instance was last scanned for vulnerabilities from the Instances tab on the Account management page or by using the [ListCoverage](https://docs.aws.amazon.com/inspector/v2/APIReference/API_ListCoverage.html) command.