AWS Security ChangesHomeSearch

AWS guardduty: Clarify connectivity troubleshooting for Bottlerocket ECS/EC2 agent

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

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

Summary

Simplified the console navigation text for coverage statistics and rewrote the 'No Agent Reporting' remediation to first determine the VPC connectivity method (guardduty-data endpoint vs link-local) with links to the new troubleshooting docs.

Security assessment

The rewrite improves remediation for instances where the GuardDuty security agent reports no data, ensuring endpoint/link-local connectivity so runtime threat detection is not degraded. Documentation of monitoring-agent connectivity requirements, not a fix for a specific vulnerability.

Evidence

+No Agent Reporting |  Not applicable |  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 instance has network connectivity to the Amazon ECR endpoint and the GuardDuty VPC endpoint. If your instance runs in a private subnet, make sure you have configured VPC endpoints for both Amazon ECR and GuardDuty. 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-bottlerocket-ecs-ec2.md b/guardduty/latest/ug/gdu-assess-coverage-bottlerocket-ecs-ec2.md
index fec8c08..a9a8437 100644
--- a//guardduty/latest/ug/gdu-assess-coverage-bottlerocket-ecs-ec2.md
+++ b//guardduty/latest/ug/gdu-assess-coverage-bottlerocket-ecs-ec2.md
@@ -13 +13 @@ For Bottlerocket Amazon EC2 instances in Amazon ECS clusters, GuardDuty evaluate
-Bottlerocket Amazon EC2 instances appear under the **EC2 instance runtime coverage** tab. To review coverage statistics for your Bottlerocket instances, open the GuardDuty console, choose **Runtime Monitoring** in the navigation pane, and then choose the **Runtime coverage** tab. Under **EC2 instance runtime coverage** , you can view the coverage status of each instance and filter by account ID, agent version, or coverage status. For more information, see [Reviewing coverage statistics](./gdu-assess-coverage-ec2.html#review-coverage-statistics-ec2-runtime-monitoring).
+Bottlerocket Amazon EC2 instances appear under the **EC2 instance runtime coverage** tab. To review their coverage statistics, see [Reviewing coverage statistics](./gdu-assess-coverage-ec2.html#review-coverage-statistics-ec2-runtime-monitoring).
@@ -35 +35 @@ No Agent Reporting |  Not applicable |  Verify that the agent host container is
-No Agent Reporting |  Not applicable |  Validate that the instance has network connectivity to the Amazon ECR endpoint and the GuardDuty VPC endpoint. If your instance runs in a private subnet, make sure you have configured VPC endpoints for both Amazon ECR and GuardDuty.  
+No Agent Reporting |  Not applicable |  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 instance has network connectivity to the Amazon ECR endpoint and the GuardDuty VPC endpoint. If your instance runs in a private subnet, make sure you have configured VPC endpoints for both Amazon ECR and GuardDuty. If your Amazon VPC has link-local connectivity, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).