AWS guardduty: GuardDuty: clarify VPC endpoint validation applies only to GuardDuty-managed endpoints
Summary
Adds a note that the endpoint validation steps apply to a GuardDuty-managed Amazon VPC endpoint, and that link-local connectivity has no endpoint to validate, with a pointer to the agent connectivity troubleshooting topic.
Security assessment
Clarifies network-path requirements (managed VPC endpoint vs. link-local connectivity) for the GuardDuty security agent to reach the service, which affects whether runtime events are actually monitored; it is operational guidance rather than a fix for a specific vulnerability.
Evidence
+These steps apply to an Amazon VPC that uses a GuardDuty-managed Amazon VPC endpoint. If your Amazon VPC uses link-local connectivity, there is no Amazon VPC endpoint to validate. For more information, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html).
Diff
diff --git a/guardduty/latest/ug/validate-vpc-endpoint-config-runtime-monitoring.md b/guardduty/latest/ug/validate-vpc-endpoint-config-runtime-monitoring.md index 9eec36c..79480be 100644 --- a//guardduty/latest/ug/validate-vpc-endpoint-config-runtime-monitoring.md +++ b//guardduty/latest/ug/validate-vpc-endpoint-config-runtime-monitoring.md @@ -10,0 +11,2 @@ After you install the security agent manually or through GuardDuty automated con +These steps apply to an Amazon VPC that uses a GuardDuty-managed Amazon VPC endpoint. If your Amazon VPC uses link-local connectivity, there is no Amazon VPC endpoint to validate. For more information, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html). +