AWS Security ChangesHomeSearch

AWS guardduty: GuardDuty ECS Fargate agent deployment docs rewritten, tag protection added

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

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

Summary

Restructures the GuardDuty Runtime Monitoring ECS Fargate page: retitles it to 'Deploying the security agent to Amazon ECS on Fargate', replaces the VPC-endpoint/security-group impact sections with a sidecar-container description (ECR/S3 image pulls, sidecar attach at task launch), and adds a 'Considerations' section covering the GuardDutyManaged tag (true/false behavior, no uninstall on false) plus new guidance to protect the GuardDutyManaged tag with SCPs or IAM policies. Related topics links were also updated.

Security assessment

The diff is primarily a documentation restructure, but it adds explicit hardening guidance: because the GuardDutyManaged tag controls whether GuardDuty deploys the runtime-monitoring agent, an attacker able to modify the tag could silently disable monitoring (a defense-evasion/visibility gap). The new bullet recommends restricting tag modification via SCPs and IAM policies, and another new bullet clarifies that setting GuardDutyManaged:false does not uninstall an already-installed agent. No specific vulnerability, CVE, or incident is referenced, so this is security-adjacent hardening guidance rather than a fix.

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-ecs-fargate.md b/guardduty/latest/ug/how-runtime-monitoring-works-ecs-fargate.md
index 934aa9d..79c3a40 100644
--- a//guardduty/latest/ug/how-runtime-monitoring-works-ecs-fargate.md
+++ b//guardduty/latest/ug/how-runtime-monitoring-works-ecs-fargate.md
@@ -7 +7 @@
-Approaches to manage GuardDuty security agent in Amazon ECS-Fargate resources
+Automated agent configuration (recommended)Related topics
@@ -9 +9 @@ Approaches to manage GuardDuty security agent in Amazon ECS-Fargate resources
-# How Runtime Monitoring works with Fargate (Amazon ECS only)
+# Deploying the security agent to Amazon ECS on Fargate
@@ -11 +11 @@ Approaches to manage GuardDuty security agent in Amazon ECS-Fargate resources
-When you enable Runtime Monitoring, GuardDuty becomes ready to consume the runtime events from a task. These tasks run within the Amazon ECS clusters, which in turn run on the AWS Fargate instances. For GuardDuty to receive these runtime events, you must use the fully-managed, dedicated security agent.
+GuardDuty Runtime Monitoring monitors your Amazon ECS clusters on Fargate for threats by deploying the GuardDuty security agent to them.
@@ -17 +17 @@ Runtime Monitoring doesn't support applications running on [Amazon ECS Managed I
-You can allow GuardDuty to manage the GuardDuty security agent on your behalf, by using Automated agent configuration for an AWS account or an organization. GuardDuty will start deploying the security agent to the new Fargate tasks that are launched in your Amazon ECS clusters. The following list specifies what to expect when you enable the GuardDuty security agent.
+GuardDuty manages the agent automatically; manual management isn't available for Fargate. In the GuardDuty console, this configuration appears as _Runtime Monitoring (ECS)_.
@@ -19 +19 @@ You can allow GuardDuty to manage the GuardDuty security agent on your behalf, b
-###### **Impact of enabling GuardDuty security agent**
+## Automated agent configuration (recommended)
@@ -21 +21 @@ You can allow GuardDuty to manage the GuardDuty security agent on your behalf, b
-**GuardDuty creates a virtual private cloud (VPC) endpoint and security group**
+GuardDuty manages deployment and updates to the security agent for new Fargate tasks in your Amazon ECS clusters.
@@ -22,0 +23 @@ You can allow GuardDuty to manage the GuardDuty security agent on your behalf, b
+For how the security agent connects to GuardDuty, see [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html).
@@ -24 +25 @@ You can allow GuardDuty to manage the GuardDuty security agent on your behalf, b
-  * When you deploy the GuardDuty security agent, GuardDuty will create a VPC endpoint through which the security agent delivers the runtime events to GuardDuty.
+**Impact of enabling the security agent**
@@ -26 +27 @@ You can allow GuardDuty to manage the GuardDuty security agent on your behalf, b
-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_.
+For each new Fargate task, GuardDuty attaches a sidecar container that runs the security agent and collects the runtime events of the containers in the task.
@@ -28 +29 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
-  * 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_.
+The sidecar image is stored in Amazon Elastic Container Registry (Amazon ECR), with layers in Amazon S3, and is pulled when the task starts. Depending on your network configuration, you might need to allow access to ECR and S3. For example, allow the S3 managed prefix list if you use restricted security groups. For more information, see [Prerequisites for container image access](./prereq-runtime-monitoring-ecs-support.html#before-enable-runtime-monitoring-ecs).
@@ -30 +31 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
-  * There is no additional cost for the usage of the VPC endpoint.
+If the sidecar can't launch, Runtime Monitoring doesn't prevent the task from running. Fargate tasks can't be modified after they start, so GuardDuty attaches the sidecar at task launch.
@@ -31,0 +33 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
+**Monitoring scope**
@@ -32,0 +35 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
+By default, GuardDuty manages the security agent for all Amazon ECS clusters in your account. To stop GuardDuty from managing the agent on a specific cluster, add the tag `GuardDutyManaged`:`false` to that cluster.
@@ -33,0 +37 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
+For more information about managing the agent for Fargate tasks, see [Managing automated security agent for Fargate (Amazon ECS only)](./managing-gdu-agent-ecs-automated.html).
@@ -35 +39 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
-**GuardDuty adds a sidecar container**
+**Considerations**
@@ -36,0 +41 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
+  * When automated agent configuration is off, GuardDuty manages the security agent only on the Amazon ECS clusters that you tag with `GuardDutyManaged`:`true`.
@@ -38 +43 @@ Along with the VPC endpoint, GuardDuty also creates a new security group. The in
-For a new Fargate task or service that starts running, a GuardDuty container (sidecar) attaches itself to each container within the Amazon ECS Fargate task. The GuardDuty security agent runs within the attached GuardDuty container. This helps GuardDuty to collect the runtime events of each container running within these tasks.
+  * Adding the `GuardDutyManaged`:`false` tag stops GuardDuty from managing the security agent, but doesn't uninstall an agent that is already installed.
@@ -40 +45 @@ For a new Fargate task or service that starts running, a GuardDuty container (si
-The GuardDuty sidecar container image is stored in Amazon Elastic Container Registry (Amazon ECR), with its image layers stored in Amazon S3. When your task starts, it needs to pull this image from ECR. Depending on your network configuration, this may require specific settings to ensure access to both ECR and S3. For example, if you're using security groups with restricted access, you'll need to allow access to the S3 managed prefix list. For more information on how to do this, see [Prerequisites for container image access](./prereq-runtime-monitoring-ecs-support.html#before-enable-runtime-monitoring-ecs).
+  * 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_.
@@ -42 +46,0 @@ The GuardDuty sidecar container image is stored in Amazon Elastic Container Regi
-When you start a Fargate task, should the GuardDuty container (sidecar) be unable to launch in a healthy state, Runtime Monitoring is designed to not prevent the tasks from running.
@@ -44 +47,0 @@ When you start a Fargate task, should the GuardDuty container (sidecar) be unabl
-By default, a Fargate task is immutable. GuardDuty will not deploy the sidecar when a task is already in a running state. If you want to monitor a container in an already running task, you can stop the task and start it again.
@@ -46 +48,0 @@ By default, a Fargate task is immutable. GuardDuty will not deploy the sidecar w
-## Approaches to manage GuardDuty security agent in Amazon ECS-Fargate resources
@@ -48 +50 @@ By default, a Fargate task is immutable. GuardDuty will not deploy the sidecar w
-Runtime Monitoring provides you the option to detect potential security threats on either all of the Amazon ECS clusters (account level) or selective clusters (cluster level) in your account. When you enable Automated agent configuration for each Amazon ECS Fargate task that will run, GuardDuty will add a sidecar container for each container workload within that task. The GuardDuty security agent gets deployed to this sidecar container. This is how GuardDuty gets visibility into the runtime behavior of the containers inside the Amazon ECS tasks.
+## Related topics
@@ -50 +52 @@ Runtime Monitoring provides you the option to detect potential security threats
-Runtime Monitoring supports managing the security agent for your Amazon ECS clusters (AWS Fargate) only through GuardDuty. There is no support for managing the security agent manually on Amazon ECS clusters.
+  * [How the security agent connects to GuardDuty](./runtime-monitoring-agent-connectivity.html)
@@ -52 +54 @@ Runtime Monitoring supports managing the security agent for your Amazon ECS clus
-Before you configure your accounts, assess if you want to monitor the runtime behavior of all the containers that belong to the Amazon ECS tasks, or include or exclude specific resources. Consider the following approaches.
+  * [Tracking Runtime Monitoring coverage](./runtime-monitoring-after-configuration.html)
@@ -54 +55,0 @@ Before you configure your accounts, assess if you want to monitor the runtime be
-**Monitor for all Amazon ECS clusters**
@@ -57,15 +57,0 @@ Before you configure your accounts, assess if you want to monitor the runtime be
-This approach will help you detect potential security threats at account level. Use this approach when you want GuardDuty to detect potential security threats for all the Amazon ECS clusters that belong to your account.
-
-**Exclude specific Amazon ECS clusters**
-    
-
-Use this approach when you want GuardDuty to detect potential security threats for most of the Amazon ECS clusters in your AWS environment but exclude some of the clusters. This approach helps you monitor the runtime behavior of the containers within your Amazon ECS tasks at the cluster level. For example, the number of Amazon ECS clusters that belong to your account are 1000\. However, you want to monitor only 930 Amazon ECS clusters.
-
-This approach requires you to add a pre-defined GuardDuty tag to the Amazon ECS clusters that you don't want to monitor. For more information, see [Managing automated security agent for Fargate (Amazon ECS only)](./managing-gdu-agent-ecs-automated.html).
-
-**Include specific Amazon ECS clusters**
-    
-
-Use this approach when you want GuardDuty to detect potential security threats for some of the Amazon ECS clusters. This approach helps you monitor the runtime behavior of the containers within your Amazon ECS tasks at the cluster level. For example, the number of Amazon ECS clusters that belong to your account are 1000. However, you want to monitor 230 clusters only.
-
-This approach requires you to add a pre-defined GuardDuty tag to the Amazon ECS clusters that you want to monitor. For more information, see [Managing automated security agent for Fargate (Amazon ECS only)](./managing-gdu-agent-ecs-automated.html).
@@ -79 +65 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-With Amazon EC2 instances
+Deploy to Amazon EC2
@@ -81 +67 @@ With Amazon EC2 instances
-After you enable Runtime Monitoring
+Agent connectivity