Ensure ECS tasks have resource limits defined
Container definitions should have CPU and memory limits to prevent resource exhaustion.
Security Impact
Without limits, a single container can consume all resources, affecting other containers.
How to Remediate
Define cpu and memory limits in container definitions based on application requirements.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Container Service (ECS) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, CIS Docker compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ecs-9
- Service
- Elastic Container Service (ECS)
- Category
- Resource Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Elastic Container Service (ECS) Checks
View all checksEnsure ECS task definitions do not run as root
Ensure ECS task definitions use read-only root filesystem
Ensure ECS task definitions do not grant privileged access
Ensure ECS task definitions do not share host namespaces
Ensure ECS task definitions have logging configured