AWS Security ChangesHomeSearch

AWS guardduty: Reword GuardDuty VPC flow log billing note for runtime agent

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

File: guardduty/latest/ug/guardduty_data-sources.md

Summary

Condenses the billing note explaining that when the GuardDuty security agent runs on an EC2 instance, VPC flow logs from that instance are not charged, avoiding double usage costs.

Security assessment

Change is a wording simplification of a pricing/billing clarification about Runtime Monitoring; no detection behavior, permission, or vulnerability is altered.

Evidence

+When the GuardDuty security agent is deployed on an Amazon EC2 instance and receives runtime events from it, GuardDuty does not charge your AWS account for analyzing VPC flow logs from that instance. This avoids double usage costs.

Diff

diff --git a/guardduty/latest/ug/guardduty_data-sources.md b/guardduty/latest/ug/guardduty_data-sources.md
index 345d433..73b23ee 100644
--- a//guardduty/latest/ug/guardduty_data-sources.md
+++ b//guardduty/latest/ug/guardduty_data-sources.md
@@ -77 +77 @@ Lambda Protection is an optional enhancement to Amazon GuardDuty. Presently, Lam
-When you manage the security agent (either manually or through GuardDuty) in EKS Runtime Monitoring or Runtime Monitoring for EC2 instances, and GuardDuty is presently deployed on an Amazon EC2 instance and receives the [Collected runtime event types](./runtime-monitoring-collected-events.html) from this instance, GuardDuty will not charge your AWS account for the analysis of VPC flow logs from this Amazon EC2 instance. This helps GuardDuty avoid double usage cost in the account.
+When the GuardDuty security agent is deployed on an Amazon EC2 instance and receives runtime events from it, GuardDuty does not charge your AWS account for analyzing VPC flow logs from that instance. This avoids double usage costs.