AWS guardduty: Clarify ECS runtime coverage and agent connectivity troubleshooting
Summary
Clarifies that ECS container instances are EC2 instances registered to the cluster, simplifies Fargate task coverage wording, and expands the 'agent not reporting' troubleshooting step to first determine VPC connectivity method (guardduty-data endpoint vs. link-local) while retaining the SCP/permissions-boundary check for guardduty:SendSecurityTelemetry.
Security assessment
Editorial clarification of ECS coverage plus added troubleshooting guidance for the security agent's network connectivity; the IAM/SCP permissions-boundary note (guardduty:SendSecurityTelemetry) is pre-existing content carried in the rewritten line, not newly introduced. No vulnerability or incident is referenced.
Evidence
Agent not reporting | Agent not reporting for tasks in `TaskDefinition - '`TASK_DEFINITION`'` | First, determine which connectivity method your Amazon VPC uses. For more information, see [Determining VPC connectivity method](./runtime-monitoring-agent-connectivity-troubleshooting.html#runtime-monitoring-link-local-which-method). If your Amazon VPC uses a `guardduty-data` Amazon VPC endpoint, validate that the VPC endpoint for your Amazon ECS cluster's task is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has link-local connectivity, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html). If your organization has a service control policy (SCP), validate that permissions boundary is not restricting the `guardduty:SendSecurityTelemetry` permission. For more information, see [Validating your organization service control policy in a multi-account environment](./prereq-runtime-monitoring-ecs-support.html#validate-organization-scp-ecs).
Diff
diff --git a/guardduty/latest/ug/gdu-assess-coverage-ecs.md b/guardduty/latest/ug/gdu-assess-coverage-ecs.md index d0515b5..0fa9e41 100644 --- a//guardduty/latest/ug/gdu-assess-coverage-ecs.md +++ b//guardduty/latest/ug/gdu-assess-coverage-ecs.md @@ -11 +11 @@ Reviewing coverage statisticsCoverage status change with EventBridge notificatio -The runtime coverage for Amazon ECS clusters includes the tasks running on AWS Fargate and Amazon ECS container instances1. +The runtime coverage for Amazon ECS clusters includes the tasks running on AWS Fargate and Amazon ECS container instances1, which are Amazon EC2 instances registered to the cluster. @@ -13 +13 @@ The runtime coverage for Amazon ECS clusters includes the tasks running on AWS F -For an Amazon ECS cluster that runs on Fargate, the runtime coverage is assessed at the task level. The ECS clusters runtime coverage includes those Fargate tasks that have started running after you have enabled Runtime Monitoring and automated agent configuration for Fargate (ECS only). By default, a Fargate task is immutable. GuardDuty will not be able to install the security agent to monitor containers on already running tasks. To include such a Fargate task, you must stop and start the task again. Make sure to check if the associated service is supported. +For an Amazon ECS cluster that runs on Fargate, the runtime coverage is assessed at the task level. Runtime Monitoring monitors tasks that start after enablement. To include a Fargate task that was already running, stop and start the task again, and check that the associated service is supported. @@ -196 +196 @@ Issue type | Extra information | Recommended troubleshooting steps -Agent not reporting | Agent not reporting for tasks in `TaskDefinition - '`TASK_DEFINITION`'` | Validate that the VPC endpoint for your Amazon ECS cluster's task is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your organization has a service control policy (SCP), validate that permissions boundary is not restricting the `guardduty:SendSecurityTelemetry` permission. For more information, see [Validating your organization service control policy in a multi-account environment](./prereq-runtime-monitoring-ecs-support.html#validate-organization-scp-ecs). +Agent not reporting | Agent not reporting for tasks in `TaskDefinition - '`TASK_DEFINITION`'` | First, determine which connectivity method your Amazon VPC uses. For more information, see [Determining VPC connectivity method](./runtime-monitoring-agent-connectivity-troubleshooting.html#runtime-monitoring-link-local-which-method). If your Amazon VPC uses a `guardduty-data` Amazon VPC endpoint, validate that the VPC endpoint for your Amazon ECS cluster's task is correctly configured. For more information, see [Validating VPC endpoint configuration](./validate-vpc-endpoint-config-runtime-monitoring.html). If your Amazon VPC has link-local connectivity, see [Troubleshooting agent connectivity](./runtime-monitoring-agent-connectivity-troubleshooting.html). If your organization has a service control policy (SCP), validate that permissions boundary is not restricting the `guardduty:SendSecurityTelemetry` permission. For more information, see [Validating your organization service control policy in a multi-account environment](./prereq-runtime-monitoring-ecs-support.html#validate-organization-scp-ecs).