AWS guardduty documentation change
Summary
Updated SCP validation link text to include 'multi-account environment' context
Security assessment
Clarification of existing security documentation without new security content.
Diff
diff --git a/guardduty/latest/ug/gdu-assess-coverage-ecs.md b/guardduty/latest/ug/gdu-assess-coverage-ecs.md index b41681b82..e3ae59e31 100644 --- a//guardduty/latest/ug/gdu-assess-coverage-ecs.md +++ b//guardduty/latest/ug/gdu-assess-coverage-ecs.md @@ -194 +194 @@ 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](./prereq-runtime-monitoring-ecs-support.html#validate-organization-scp-ecs). +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).