AWS Security ChangesHomeSearch

AWS guardduty: Clarify EC2 runtime coverage and agent connectivity troubleshooting

Service: guardduty · 2026-10-30 · Documentation low

File: guardduty/latest/ug/gdu-assess-coverage-ec2.md · Type: network

Summary

Rewrites EC2 runtime coverage wording (instance-level status for ECS-on-EC2 clusters, coverage statistic definition) and expands the 'agent not reporting' troubleshooting step to first determine the VPC connectivity method (guardduty-data VPC endpoint vs. link-local) before validating endpoint configuration.

Security assessment

The change is documentation-only: it clarifies coverage statistics and adds a troubleshooting branch for the GuardDuty security agent's network path (VPC endpoint vs. link-local). It helps operators restore agent telemetry connectivity, which supports detection, but it fixes no vulnerability and introduces no new security control.

Evidence

First, determine which connectivity method your Amazon VPC uses. For more information, see [Determining VPC connectivity method](./runtime-monitoring-agent-connectivity-troubleshooting.html#runtime-monitoring-link-local-which-method). If your Amazon VPC uses a `guardduty-data` Amazon VPC endpoint, validate that the VPC endpoint for your Amazon EC2 instance is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has link-local connectivity, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).

Diff

diff --git a/guardduty/latest/ug/gdu-assess-coverage-ec2.md b/guardduty/latest/ug/gdu-assess-coverage-ec2.md
index edd1e49..d83a053 100644
--- a//guardduty/latest/ug/gdu-assess-coverage-ec2.md
+++ b//guardduty/latest/ug/gdu-assess-coverage-ec2.md
@@ -11 +11 @@ Reviewing coverage statisticsCoverage status change with EventBridge notificatio
-For an Amazon EC2 resource, the runtime coverage is evaluated at the instance level. Your Amazon EC2 instances can run multiple types of applications and workloads amongst others in your AWS environment. This feature also supports Amazon ECS managed Amazon EC2 instances and if you have Amazon ECS clusters running on an Amazon EC2 instance, the coverage issues at the instance level will show up under Amazon EC2 runtime coverage. 
+For an Amazon EC2 resource, the runtime coverage is evaluated at the instance level. Coverage for Amazon EC2 also reflects the instance-level status for Amazon ECS clusters running on Amazon EC2 instances.
@@ -26 +26 @@ For an Amazon EC2 resource, the runtime coverage is evaluated at the instance le
-The coverage statistics for the Amazon EC2 instances associated with your own accounts or your member accounts is the percentage of the healthy EC2 instances over all EC2 instances in the selected AWS Region. The following equation represents this as:
+The coverage statistic for Amazon EC2 instances in your account and member accounts is the percentage of healthy instances in the selected AWS Region:
@@ -30,2 +29,0 @@ _(Healthy instances/All instances)*100_
-If you have also deployed the GuardDuty security agent for your Amazon ECS clusters, then any instance level coverage issue associated with Amazon ECS clusters running on an Amazon EC2 instance will appear as an Amazon EC2 instance runtime coverage issue. 
-
@@ -197 +195 @@ If you've enabled automated agent configuration:
-Validate that the VPC endpoint for your Amazon EC2 instance is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html).  
+First, determine which connectivity method your Amazon VPC uses. For more information, see [Determining VPC connectivity method](./runtime-monitoring-agent-connectivity-troubleshooting.html#runtime-monitoring-link-local-which-method). If your Amazon VPC uses a `guardduty-data` Amazon VPC endpoint, validate that the VPC endpoint for your Amazon EC2 instance is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has link-local connectivity, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).