AWS Security ChangesHomeSearch

AWS guardduty: Restructure GuardDuty EC2 Runtime Monitoring agent deployment page

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

File: guardduty/latest/ug/how-runtime-monitoring-works-ec2.md · Type: iam

Summary

Rewrites the GuardDuty Runtime Monitoring EC2 page: retitles it to 'Deploying the security agent to Amazon EC2', condenses the automated vs. manual agent configuration sections, drops the detailed VPC endpoint/security-group creation bullets, and adds new guidance on tag-based monitoring scope and protecting the GuardDutyManaged tag with SCPs/IAM policies.

Security assessment

The added bullet explicitly advises restricting who can modify the GuardDutyManaged tag via SCPs/IAM policies, because that tag controls whether GuardDuty stops managing the security agent on an instance (defense evasion by disabling monitoring). This is authorization-hardening guidance and a security best practice, but there is no evidence of a fixed vulnerability, CVE, or incident, so it is documentation-only security guidance.

Evidence

  * Protect the `GuardDutyManaged` tag by controlling who can modify it, using service control policies or IAM policies. For more information, see [Service control policies (SCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the _AWS Organizations User Guide_ or [Control access to AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags.html) in the _IAM User Guide_.

Diff

diff --git a/guardduty/latest/ug/how-runtime-monitoring-works-ec2.md b/guardduty/latest/ug/how-runtime-monitoring-works-ec2.md
index 2399e44..1507022 100644
--- a//guardduty/latest/ug/how-runtime-monitoring-works-ec2.md
+++ b//guardduty/latest/ug/how-runtime-monitoring-works-ec2.md
@@ -7 +7 @@
-Use automated agent configuration (recommended)Manage security agent manuallyNext step
+Automated agent configuration (recommended)Manual agent configurationRelated topics
@@ -9 +9 @@ Use automated agent configuration (recommended)Manage security agent manuallyNex
-# How Runtime Monitoring works with Amazon EC2 instances
+# Deploying the security agent to Amazon EC2
@@ -11 +11 @@ Use automated agent configuration (recommended)Manage security agent manuallyNex
-Your Amazon EC2 instances can run multiple types of applications and workloads in your AWS environment. When you enable Runtime Monitoring and manage the GuardDuty security agent, GuardDuty helps you detect threats in your existing Amazon EC2 instances and potentially new ones. This feature also supports Amazon ECS Managed EC2 Instances.
+GuardDuty Runtime Monitoring monitors your Amazon EC2 instances for threats by deploying the GuardDuty security agent to them.
@@ -15 +15 @@ Your Amazon EC2 instances can run multiple types of applications and workloads i
-Runtime Monitoring doesn't support applications running on [Amazon ECS Managed Instances](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ManagedInstances.html).
+Runtime Monitoring also collects runtime events from Amazon ECS tasks running on your Amazon EC2 instances.
@@ -17 +17 @@ Runtime Monitoring doesn't support applications running on [Amazon ECS Managed I
-Enabling Runtime Monitoring makes GuardDuty ready to consume runtime events from currently running and new processes within Amazon EC2 instances. GuardDuty requires a security agent to send runtime events from your EC2 instance to GuardDuty. 
+You can let GuardDuty manage the agent automatically (recommended) or manage it manually.
@@ -19 +19 @@ Enabling Runtime Monitoring makes GuardDuty ready to consume runtime events from
-For Amazon EC2 instances, GuardDuty security agent operates at the instance level. You can decide if you want to monitor all or selective Amazon EC2 instances in your account. If you want to manage selective instances, the security agent is required only for these instances.
+## Automated agent configuration (recommended)
@@ -21 +21 @@ For Amazon EC2 instances, GuardDuty security agent operates at the instance leve
-GuardDuty can also consume runtime events from new tasks and existing tasks running in Amazon EC2 instances within Amazon ECS clusters. 
+GuardDuty manages deployment and updates to the security agent for your Amazon EC2 instances. In the GuardDuty console, this configuration appears as _Runtime Monitoring (EC2)_.
@@ -23 +23 @@ GuardDuty can also consume runtime events from new tasks and existing tasks runn
-To install the GuardDuty security agent, Runtime Monitoring provides the following two options:
+For how the security agent connects to GuardDuty, see [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html).
@@ -25 +25 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
-  * Use automated agent configuration (recommended), or
+**Impact of enabling the security agent**
@@ -27 +27 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
-  * Manage security agent manually
+With automated agent configuration, GuardDuty creates one SSM association for your SSM-managed Amazon EC2 instances (shown under **Fleet Manager** in the [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/) console) and uses it to install and update the agent.
@@ -28,0 +29 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
+**Monitoring scope**
@@ -29,0 +31 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
+By default, GuardDuty manages the security agent for all Amazon EC2 instances in your account. To stop GuardDuty from managing the agent on a specific instance, add the tag `GuardDutyManaged`:`false` to that instance.
@@ -30,0 +33 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
+**Considerations**
@@ -32 +35 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
-## Use automated agent configuration through GuardDuty (recommended)
+  * When automated agent configuration is off, GuardDuty manages the security agent only on the Amazon EC2 instances that you tag with `GuardDutyManaged`:`true`.
@@ -34 +37 @@ To install the GuardDuty security agent, Runtime Monitoring provides the followi
-Use automated agent configuration that permits GuardDuty to install the security agent on your Amazon EC2 instances on your behalf. GuardDuty also manages the updates to the security agent.
+  * Adding the `GuardDutyManaged`:`false` tag stops GuardDuty from managing the security agent, but doesn't uninstall an agent that is already installed.
@@ -36 +39 @@ Use automated agent configuration that permits GuardDuty to install the security
-By default, GuardDuty installs the security agent on all the instances in your account. If you'd want GuardDuty to install and manage the security agent for selected EC2 instances only, add inclusion or exclusion tags to your EC2 instances, as needed.
+  * Protect the `GuardDutyManaged` tag by controlling who can modify it, using service control policies or IAM policies. For more information, see [Service control policies (SCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the _AWS Organizations User Guide_ or [Control access to AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags.html) in the _IAM User Guide_.
@@ -38 +40,0 @@ By default, GuardDuty installs the security agent on all the instances in your a
-Sometimes, you may not want to monitor runtime events for all the Amazon EC2 instances that belong to your account. For cases when you want to monitor the runtime events for a limited number of instances, add an inclusion tag as `GuardDutyManaged`:`true` to these selected instances. Starting with the availability of automated agent configuration for Amazon EC2, if your EC2 instance has an inclusion tag (`GuardDutyManaged`:`true`), GuardDuty will honor the tag and manage the security agent for the selected instances even when you do not explicitly enable automated agent configuration.
@@ -40 +41,0 @@ Sometimes, you may not want to monitor runtime events for all the Amazon EC2 ins
-On the other hand, if there are a limited number of EC2 instances for which you don't want to monitor runtime events, add an exclusion tag (`GuardDutyManaged`:`false`) to these selected instances. GuardDuty will honor the exclusion tag by **neither** installing **nor** managing the security agent for these EC2 resources.
@@ -42 +42,0 @@ On the other hand, if there are a limited number of EC2 instances for which you
-### Impact
@@ -44 +44 @@ On the other hand, if there are a limited number of EC2 instances for which you
-When you use automated agent configuration in an AWS account or an organization, you permit GuardDuty to take the following steps on your behalf:
+## Manual agent configuration
@@ -46,13 +46 @@ When you use automated agent configuration in an AWS account or an organization,
-  * GuardDuty creates one SSM association for all your Amazon EC2 instances that are SSM managed and appear under **Fleet Manager** in the [https://console.aws.amazon.com/systems-manager/](https://console.aws.amazon.com/systems-manager/) console. 
-
-  * Using inclusion tags with automated agent configuration disabled – After enabling Runtime Monitoring, when you don't enable automated agent configuration but add inclusion tag to your Amazon EC2 instance, it means that you are permitting GuardDuty to manage the security agent on your behalf. SSM association will then install the security agent in each instance that has the inclusion tag (`GuardDutyManaged`:`true`).
-
-  * If you enable automated agent configuration – The SSM association will then install the security agent in all the EC2 instances that belong to your account. 
-
-  * Using exclusion tags with automated agent configuration – Before you enable automated agent configuration, when you add exclusion tag to your Amazon EC2 instance, it means that you are permitting GuardDuty to prevent installing and managing the security agent for this selected instance.
-
-Now, when you enable automated agent configuration, the SSM association will install and manage the security agent in all the EC2 instances except the ones that are tagged with the exclusion tag. 
-
-  * GuardDuty creates VPC endpoints in all the VPCs, including shared VPCs, as long as there is at least one Linux EC2 instance in that VPC that are not in the terminated or shutting-down instance states. This includes the centralized VPC and spoke VPCs. GuardDuty doesn't support creating a VPC endpoint only for the centralized VPC. For more information about how the centralized VPC works, see [Interface VPC endpoints](https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/centralized-access-to-vpc-private-endpoints.html#interface-vpc-endpoints) in the _AWS Whitepaper - Building a Scalable and Secure Multi-VPC AWS Network Infrastructure_.
-
-For information about different instance states, see [Instance lifecycle](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-lifecycle.html) in the _Amazon EC2 User Guide_.
+There are two ways to manage the security agent for Amazon EC2 manually:
@@ -60 +48 @@ For information about different instance states, see [Instance lifecycle](https:
-GuardDuty also supports [Using shared VPC with Runtime Monitoring](./runtime-monitoring-shared-vpc.html). When all the prerequisites are considered for your organization and AWS account, GuardDuty will use the shared VPC to receive runtime events.
+  * For SSM-managed Amazon EC2 instances, you can use GuardDuty managed documents in AWS Systems Manager to install the security agent.
@@ -64 +52 @@ GuardDuty also supports [Using shared VPC with Runtime Monitoring](./runtime-mon
-There is no additional cost for the usage of the VPC endpoint.
+To use this option, ensure that each new Amazon EC2 instance you launch is SSM enabled.
@@ -66,6 +54 @@ There is no additional cost for the usage of the VPC endpoint.
-  * Along with the VPC endpoint, GuardDuty also creates a new security group. The inbound (ingress) rules control the traffic that's allowed to reach the resources, that are associated with the security group. GuardDuty adds inbound rules that match the VPC CIDR range for your resource, and also adapts to it when the CIDR range changes. For more information, see [VPC CIDR range](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html) in the _Amazon VPC User Guide_.
-
-
-
-
-## Manage security agent manually
+  * Use RPM package manager (RPM) scripts to install the security agent on your Amazon EC2 instances, whether or not they are SSM managed.
@@ -73 +55,0 @@ There is no additional cost for the usage of the VPC endpoint.
-There are two ways to manage the security agent for Amazon EC2 manually:
@@ -75 +56,0 @@ There are two ways to manage the security agent for Amazon EC2 manually:
-  * Use GuardDuty managed documents in AWS Systems Manager to install the security agent on your Amazon EC2 instances that are already SSM managed.
@@ -77 +57,0 @@ There are two ways to manage the security agent for Amazon EC2 manually:
-Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
@@ -79 +59 @@ Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
-  * Use RPM package manager (RPM) scripts to install the security agent on your Amazon EC2 instances, whether or not they are SSM managed.
+## Related topics
@@ -80,0 +61 @@ Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
+  * [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html)
@@ -81,0 +63 @@ Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
+  * [Tracking Runtime Monitoring coverage](./runtime-monitoring-after-configuration.html)
@@ -84 +65,0 @@ Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
-## Next step
@@ -86 +66,0 @@ Whenever you launch a new Amazon EC2 instance, ensure that it is SSM enabled.
-To get started with Runtime Monitoring configuration to monitor your Amazon EC2 instances, see [Prerequisites for Amazon EC2 instance support](./prereq-runtime-monitoring-ec2-support.html).
@@ -94 +74 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-With Amazon EKS clusters
+Deploy to Amazon EKS
@@ -96 +76 @@ With Amazon EKS clusters
-With Fargate (Amazon ECS only)
+Deploy to Amazon ECS on Fargate