AWS Security ChangesHomeSearch

AWS guardduty: GuardDuty EKS Runtime Monitoring agent deployment docs restructured

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

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

Summary

Restructures EKS Runtime Monitoring agent deployment guidance into automated and manual configuration, and adds guidance to protect the GuardDutyManaged tag with SCPs/IAM policies.

Security assessment

The added line advises controlling who can modify the GuardDutyManaged tag via SCPs/IAM policies, a hardening best practice to prevent unauthorized disabling of agent management; no specific vulnerability or CVE is referenced.

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-eks.md b/guardduty/latest/ug/how-runtime-monitoring-works-eks.md
index c18423c..c4cc421 100644
--- a//guardduty/latest/ug/how-runtime-monitoring-works-eks.md
+++ b//guardduty/latest/ug/how-runtime-monitoring-works-eks.md
@@ -7 +7 @@
-Approaches to manage GuardDuty security agent in Amazon EKS clusters
+Automated agent configuration (recommended)Manual agent configurationRelated topics
@@ -9 +9 @@ Approaches to manage GuardDuty security agent in Amazon EKS clusters
-# How Runtime Monitoring works with Amazon EKS clusters
+# Deploying the security agent to Amazon EKS
@@ -11 +11 @@ Approaches to manage GuardDuty security agent in Amazon EKS clusters
-Runtime Monitoring uses an [EKS add-on `aws-guardduty-agent`](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html#workloads-add-ons-available-eks), also known as the GuardDuty security agent. After GuardDuty security agent gets deployed on your EKS clusters, GuardDuty is able to receive runtime events for these EKS clusters. 
+GuardDuty Runtime Monitoring monitors your Amazon EKS clusters for threats by deploying the GuardDuty security agent to them. On Amazon EKS, GuardDuty deploys the agent as the [EKS add-on `aws-guardduty-agent`](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html#workloads-add-ons-available-eks).
@@ -21 +21 @@ For information about these Amazon EKS features, see [What is Amazon EKS?](https
-You can monitor the runtime events of your Amazon EKS clusters at either account or cluster level. You can manage the GuardDuty security agent for only those Amazon EKS clusters that you want to monitor for threat detection. You can manage the GuardDuty security agent either manually or by allowing GuardDuty to manage it on your behalf, by using Automated agent configuration.
+You can let GuardDuty manage the agent automatically (recommended) or manage it manually.
@@ -23 +23 @@ You can monitor the runtime events of your Amazon EKS clusters at either account
-When you use the automated agent configuration approach to allow GuardDuty to manage the deployment of the security agent on your behalf, it will automatically **create an Amazon Virtual Private Cloud (Amazon VPC) endpoint**. The security agent delivers the runtime events to GuardDuty by using this Amazon VPC endpoint. 
+## Automated agent configuration (recommended)
@@ -25 +25 @@ When you use the automated agent configuration approach to allow GuardDuty to ma
-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_.
+GuardDuty manages deployment and updates to the security agent for your EKS clusters. In the GuardDuty console, this configuration appears as _Runtime Monitoring (EKS)_.
@@ -27,51 +27 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
-###### Notes
-
-  * There is no additional cost for the usage of the VPC endpoint.
-
-  * Working with centralized VPC with automated agent – When you use GuardDuty automated agent configuration for a resource type, GuardDuty will create a VPC endpoint on your behalf for all the VPCs. 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_.
-
-
-
-
-## Approaches to manage GuardDuty security agent in Amazon EKS clusters
-
-Prior to September 13, 2023, you could configure GuardDuty to manage the security agent at the account level. This behavior indicated that by default, GuardDuty manages the security agent on all the EKS clusters that belong to an AWS account. Now, GuardDuty provides a granular capability to help you choose the EKS clusters where you want GuardDuty to manage the security agent.
-
-When you choose to Manage GuardDuty security agent manually, you can still select the EKS clusters that you want to monitor. However, to manage the agent manually, creating a Amazon VPC endpoint for your AWS account is a prerequisite.
-
-###### Note
-
-Regardless of the approach that you use to manage the GuardDuty security agent, EKS Runtime Monitoring is always enabled at the account level. 
-
-###### Topics
-
-  * Manage security agent through GuardDuty
-
-  * Manage GuardDuty security agent manually
-
-
-
-
-### Manage security agent through GuardDuty
-
-GuardDuty deploys and manages the security agent on your behalf. At any point in time, you can monitor the EKS clusters in your account by using one of the following approaches.
-
-###### Topics
-
-  * Monitor all EKS clusters
-
-  * Exclude selective EKS clusters
-
-  * Include selective EKS clusters
-
-
-
-
-#### Monitor all EKS clusters
-
-Use this approach when you want GuardDuty to deploy and manage the security agent for all the EKS clusters in your account. By default, GuardDuty will also deploy the security agent on a potentially new EKS cluster created in your account.
-
-**Impact of using this approach**
-    
-
-  * GuardDuty creates an Amazon Virtual Private Cloud (Amazon VPC) endpoint through which the GuardDuty security agent delivers the runtime events to GuardDuty. There is no additional cost for the creation of the Amazon VPC endpoint when you manage the security agent through GuardDuty.
+For how the security agent connects to GuardDuty, see [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html).
@@ -79 +29 @@ Use this approach when you want GuardDuty to deploy and manage the security agen
-  * It is required that your worker node has a valid network path to an active `guardduty-data` VPC endpoint. GuardDuty deploys the security agent on your EKS clusters. Amazon Elastic Kubernetes Service (Amazon EKS) will coordinate the deployment of the security agent on the nodes within the EKS clusters.
+**Impact of enabling the security agent**
@@ -81 +31 @@ Use this approach when you want GuardDuty to deploy and manage the security agen
-  * On the basis of IP availability, GuardDuty selects the subnet to create a VPC endpoint. If you use advanced network topologies, you must validate that the connectivity is possible.
+GuardDuty deploys the security agent to your EKS clusters, and Amazon Elastic Kubernetes Service (Amazon EKS) coordinates deploying it to the nodes.
@@ -82,0 +33 @@ Use this approach when you want GuardDuty to deploy and manage the security agen
+**Monitoring scope**
@@ -83,0 +35 @@ Use this approach when you want GuardDuty to deploy and manage the security agen
+By default, GuardDuty manages the security agent for all EKS clusters in your account, including new clusters you create. To stop GuardDuty from managing the agent on a specific cluster, add the tag `GuardDutyManaged`:`false` to that cluster.
@@ -85,11 +37 @@ Use this approach when you want GuardDuty to deploy and manage the security agen
-
-#### Exclude selective EKS clusters
-
-Use this approach when you want GuardDuty to manage the security agent for all EKS clusters in your account but exclude selective EKS clusters. This method uses a tag-based1 approach wherein you can tag the EKS clusters for which you don't want to receive the runtime events. The pre-defined tag must have `GuardDutyManaged`:`false` as the key-value pair.
-
-**Impact of using this approach**
-    
-
-This approach requires that you enable GuardDuty agent auto-management only after adding tags to the EKS clusters that you want to exclude from monitoring.
-
-Therefore, the impact when you Manage security agent through GuardDuty applies to this approach too. When you add tags prior to enabling GuardDuty agent auto-management, GuardDuty will neither deploy nor manage the security agent for the EKS clusters that are excluded from monitoring.
+For more information about tagging EKS clusters, see [Tagging your Amazon EKS resources](https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html) in the __Amazon EKS User Guide__.
@@ -98,0 +41 @@ Therefore, the impact when you Manage security agent through GuardDuty applies t
+  * When automated agent configuration is off, GuardDuty manages the security agent only on the EKS clusters that you tag with `GuardDutyManaged`:`true`.
@@ -100,3 +43 @@ Therefore, the impact when you Manage security agent through GuardDuty applies t
-  * You must add the tag key-value pair as `GuardDutyManaged`:`false` for the selective EKS clusters before enabling Automated agent configuration otherwise, the GuardDuty security agent will be deployed on all the EKS clusters until you use the tag.
-
-  * You must prevent the tags from being modified, except by trusted identities.
+  * Adding the `GuardDutyManaged`:`false` tag stops GuardDuty from managing the security agent, but doesn't uninstall an agent that is already installed.
@@ -104 +45 @@ Therefore, the impact when you Manage security agent through GuardDuty applies t
-###### Important
+  * 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_.
@@ -106 +46,0 @@ Therefore, the impact when you Manage security agent through GuardDuty applies t
-Manage permissions for modifying the value of the `GuardDutyManaged` tag for your EKS cluster by 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_.
@@ -108 +47,0 @@ Manage permissions for modifying the value of the `GuardDutyManaged` tag for you
-  * For a potentially new EKS cluster that you don't want to monitor, make sure to add the `GuardDutyManaged`:`false` key-value pair at the time of creating this EKS cluster.
@@ -110 +48,0 @@ Manage permissions for modifying the value of the `GuardDutyManaged` tag for you
-  * This approach will also have the same consideration as specified for Monitor all EKS clusters.
@@ -111,0 +50 @@ Manage permissions for modifying the value of the `GuardDutyManaged` tag for you
+## Manual agent configuration
@@ -113,5 +52 @@ Manage permissions for modifying the value of the `GuardDutyManaged` tag for you
-
-
-#### Include selective EKS clusters
-
-Use this approach when you want GuardDuty to deploy and manage the updates to the security agent only for selective EKS clusters in your account. This method uses a tag-based1 approach wherein you can tag the EKS cluster for which you want to receive the runtime events.
+Use this approach when you want to manually deploy and manage the GuardDuty security agent on all your EKS clusters. Ensure Runtime Monitoring is enabled for your accounts. The GuardDuty security agent might not work as expected if Runtime Monitoring isn't enabled.
@@ -121,7 +56 @@ Use this approach when you want GuardDuty to deploy and manage the updates to th
-
-  * By using inclusion tags, GuardDuty will automatically deploy and manage the security agent only for the selective EKS clusters that are tagged with `GuardDutyManaged`:`true` as the key-value pair.
-
-  * Using this approach will also have the same impact as specified for Monitor all EKS clusters. 
-
-
-
+You must coordinate deploying the GuardDuty security agent within your EKS clusters across all your accounts. To get the latest security features, you must also update the agent when GuardDuty releases a new version. For more information about agent versions for EKS, see [GuardDuty security agent versions for Amazon EKS resources](./runtime-monitoring-agent-release-history.html#eks-runtime-monitoring-agent-release-history).
@@ -130,0 +60 @@ Use this approach when you want GuardDuty to deploy and manage the updates to th
+You must support secure data flow while monitoring for and addressing coverage gaps as new clusters and workloads are continuously deployed.
@@ -132,22 +62 @@ Use this approach when you want GuardDuty to deploy and manage the updates to th
-  * If the value of the `GuardDutyManaged` tag is not set to `true`, the inclusion tag will not work as expected and this may impact monitoring your EKS cluster.
-
-  * To ensure that your selective EKS clusters are being monitored, you need to prevent the tags from being modified, except by trusted identities.
-
-###### Important
-
-Manage permissions for modifying the value of the `GuardDutyManaged` tag for your EKS cluster by 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_.
-
-  * For a potentially new EKS cluster that you don't want to monitor, make sure to add the `GuardDutyManaged`:`false` key-value pair at the time of creating this EKS cluster.
-
-  * This approach will also have the same consideration as specified for Monitor all EKS clusters.
-
-
-
-
-1For more information about tagging selective EKS clusters, see [Tagging your Amazon EKS resources](https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html) in the __Amazon EKS User Guide__.
-
-### Manage GuardDuty security agent manually
-
-Use this approach when you want to deploy and manage the GuardDuty security agent on all of your EKS clusters manually. Ensure that EKS Runtime Monitoring is enabled for your accounts. The GuardDuty security agent may not work as expected if you don't enable EKS Runtime Monitoring.
-
-**Impact of using this approach**
+## Related topics
@@ -154,0 +64 @@ Use this approach when you want to deploy and manage the GuardDuty security agen
+  * [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html)
@@ -156 +66 @@ Use this approach when you want to deploy and manage the GuardDuty security agen
-You will need to coordinate the deployment of the GuardDuty security agent within your EKS clusters across all accounts and AWS Regions where this feature is available. You will also need to update the agent version when GuardDuty releases it. For more information about agent versions for EKS, see [GuardDuty security agent versions for Amazon EKS resources](./runtime-monitoring-agent-release-history.html#eks-runtime-monitoring-agent-release-history).
+  * [Tracking Runtime Monitoring coverage](./runtime-monitoring-after-configuration.html)
@@ -158 +67,0 @@ You will need to coordinate the deployment of the GuardDuty security agent withi
-**Considerations**
@@ -161 +69,0 @@ You will need to coordinate the deployment of the GuardDuty security agent withi
-You must support secure data flow while monitoring for and addressing coverage gaps as new clusters and workloads are continuously deployed.
@@ -169 +77 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-How it works
+Enablement
@@ -171 +79 @@ How it works
-With Amazon EC2 instances
+Deploy to Amazon EC2