AWS Security ChangesHomeSearch

AWS guardduty: Runtime Monitoring page retitled and section removed

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

File: guardduty/latest/ug/runtime-monitoring-after-configuration.md

Summary

Renamed the page heading to 'Tracking Runtime Monitoring coverage', removed the 'GuardDuty detects potential threats' section, and changed a coverage label to 'Agent connectivity'.

Security assessment

Editorial restructuring of headings and removal of a descriptive paragraph; no new security controls or vulnerability fixes are documented.

Evidence

-# After you enable Runtime Monitoring

Diff

diff --git a/guardduty/latest/ug/runtime-monitoring-after-configuration.md b/guardduty/latest/ug/runtime-monitoring-after-configuration.md
index 6a3c7d0..1893d37 100644
--- a//guardduty/latest/ug/runtime-monitoring-after-configuration.md
+++ b//guardduty/latest/ug/runtime-monitoring-after-configuration.md
@@ -7 +7 @@
-# After you enable Runtime Monitoring
+# Tracking Runtime Monitoring coverage
@@ -25,5 +24,0 @@ After you have assessed that the coverage status shows as **Healthy** , you can
-**GuardDuty detects potential threats**
-    
-
-As GuardDuty starts to receive the runtime events for your resource, it starts analyzing those events. When GuardDuty detects a potential security threat in any of your Amazon EC2 instances, Amazon ECS clusters, or Amazon EKS clusters, it generates one or more [GuardDuty Runtime Monitoring finding types](./findings-runtime-monitoring.html). You can access the finding details to view the impacted resource details.
-
@@ -36 +31 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-With Fargate (Amazon ECS only)
+Agent connectivity