AWS Security ChangesHomeSearch

AWS guardduty: Add link-local vs VPC endpoint guidance for GuardDuty agent

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

File: guardduty/latest/ug/eks-runtime-monitoring-coverage.md · Type: network

Summary

Extended the EKS runtime monitoring troubleshooting guidance to note that a VPC without a guardduty-data endpoint may use link-local connectivity, linking to new connectivity troubleshooting docs, and updated the related topic link text.

Security assessment

Guidance targets keeping the GuardDuty Runtime Monitoring security agent connected so detection coverage is not silently lost (e.g., shared VPCs without guardduty-data endpoints). It is operational security-hardening documentation rather than a fix for a specific vulnerability.

Evidence

+  * When you manage the security agent manually, confirm that you created a VPC endpoint for all the VPCs. When you enable GuardDuty automated configuration, you should still validate that the VPC endpoint gets created. For example, when using a shared VPC in automated configuration. To validate this, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has no `guardduty-data` Amazon VPC endpoint, it might use link-local connectivity instead. To check, and to troubleshoot it, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).

Diff

diff --git a/guardduty/latest/ug/eks-runtime-monitoring-coverage.md b/guardduty/latest/ug/eks-runtime-monitoring-coverage.md
index 635469d..9736df8 100644
--- a//guardduty/latest/ug/eks-runtime-monitoring-coverage.md
+++ b//guardduty/latest/ug/eks-runtime-monitoring-coverage.md
@@ -227 +227 @@ EKS Addon Issue - `InsufficientNumberOfReplicas`: The add-on is unhealthy becaus
-  * When you manage the security agent manually, confirm that you created a VPC endpoint for all the VPCs. When you enable GuardDuty automated configuration, you should still validate that the VPC endpoint gets created. For example, when using a shared VPC in automated configuration. To validate this, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html).
+  * When you manage the security agent manually, confirm that you created a VPC endpoint for all the VPCs. When you enable GuardDuty automated configuration, you should still validate that the VPC endpoint gets created. For example, when using a shared VPC in automated configuration. To validate this, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has no `guardduty-data` Amazon VPC endpoint, it might use link-local connectivity instead. To check, and to troubleshoot it, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).
@@ -284 +284 @@ Coverage and troubleshooting for Amazon ECS clusters
-Setting up CPU and memory monitoring
+Troubleshooting agent connectivity