AWS AmazonECS medium security documentation change
Summary
Clarified GuardDuty integration details and added explicit note about Runtime Monitoring unsupported on Managed Instances
Security assessment
Explicitly stating that Runtime Monitoring isn't supported on Managed Instances helps prevent security monitoring gaps. This addresses potential misconfigurations that could lead to undetected security issues.
Diff
diff --git a/AmazonECS/latest/developerguide/ecs-guard-duty-integration.md b/AmazonECS/latest/developerguide/ecs-guard-duty-integration.md index be473509d..ab8112d6e 100644 --- a//AmazonECS/latest/developerguide/ecs-guard-duty-integration.md +++ b//AmazonECS/latest/developerguide/ecs-guard-duty-integration.md @@ -44 +44 @@ The response parameters include the Runtime Monitoring tag (when the tag is set) -For the Fargate launch type, the response parameters include the GuardDuty sidecar container. +For Fargate, the response parameters include the GuardDuty sidecar container. @@ -52 +52 @@ The response parameters include the Runtime Monitoring account setting, which is - * The task metadata endpoint for the launch type: + * The task metadata endpoint for the compute option: @@ -78,0 +79,2 @@ Consider the following when using Runtime Monitoring: + * Runtime Monitoring is not supported for applications running on Amazon ECS Managed Instances. +