AWS guardduty: GuardDuty: rewrite Runtime Monitoring coverage status wording and add connectivity troubleshooting link
Summary
Replaces the coverage-status explanation with a clearer, agent-connectivity-centric description (per resource type: EKS clusters, EC2 instances, ECS clusters) and adds a link to the new 'Troubleshooting agent connectivity' topic in the topic list.
Security assessment
Documentation for a threat-detection feature (Runtime Monitoring) that explains when GuardDuty can receive runtime events; clarifies that Unhealthy coverage means events are neither received, monitored, nor turned into findings. No specific vulnerability or incident is addressed, only clarity of detection-coverage guidance.
Evidence
+After you enable Runtime Monitoring and the GuardDuty security agent is deployed to your resource, GuardDuty provides coverage statistics per resource type (EKS clusters, EC2 instances, ECS clusters) and a coverage status for each resource in your account.
Diff
diff --git a/guardduty/latest/ug/runtime-monitoring-assessing-coverage.md b/guardduty/latest/ug/runtime-monitoring-assessing-coverage.md index 7502636..c98f9c3 100644 --- a//guardduty/latest/ug/runtime-monitoring-assessing-coverage.md +++ b//guardduty/latest/ug/runtime-monitoring-assessing-coverage.md @@ -9 +9 @@ -After you enable Runtime Monitoring and the GuardDuty security agent gets deployed to your resource, GuardDuty provides coverage statistics for the corresponding resource type and individual coverage status for the resources that belong to your account. Coverage status is determined by making sure that you have enabled Runtime Monitoring, your Amazon VPC endpoint has been created, and the GuardDuty security agent for the corresponding resource has been deployed. A **Healthy** coverage status indicates that when there is a runtime event related to your resource, GuardDuty is able to receive the said runtime event through the Amazon VPC endpoint, and monitor the behavior. If there was an issue at the time of configuring Runtime Monitoring, creating an Amazon VPC endpoint, or deploying the GuardDuty security agent, the coverage status appears as **Unhealthy**. When the coverage status is unhealthy, GuardDuty will not be able to receive or monitor the runtime behavior of the corresponding resource, or generate any Runtime Monitoring findings. +After you enable Runtime Monitoring and the GuardDuty security agent is deployed to your resource, GuardDuty provides coverage statistics per resource type (EKS clusters, EC2 instances, ECS clusters) and a coverage status for each resource in your account. GuardDuty determines coverage status by checking that you have enabled Runtime Monitoring, that you have deployed the security agent, and that the security agent can connect to GuardDuty. A **Healthy** coverage status indicates that GuardDuty is able to receive runtime events from the monitored resource. An **Unhealthy** status indicates an issue with configuring Runtime Monitoring, deploying the security agent, or the security agent connecting to GuardDuty. When the coverage status is unhealthy, GuardDuty can't receive or monitor the runtime behavior of the resource, or generate Runtime Monitoring findings. @@ -22,0 +23,2 @@ The following topics will help you review coverage statistics, configure EventBr + * [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html) +