Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
ecs_task_definitions_logging_enabledProvider: AWS
Service:
ecsSeverity: HIGH
Categories:
loggingResource type:
AwsEcsTaskDefinitionWhat this check verifies
Amazon ECS task definition containers specify a logging configuration with a non-nulllogDriver for every container in the latest active revision.
Risk
Absent container logs erode visibility, letting intrusions, data exfiltration, and configuration tampering go undetected. Missing audit trails weaken confidentiality and integrity, hinder forensics, and increase MTTR during outages, impacting availability and compliance evidence.Recommendation
Implement centralized, tamper-resistant container logging for all tasks. Define alogDriver per container and ship logs to a managed destination with restricted access. Apply least privilege, encryption, and retention. Monitor and alert on anomalies. If using external collectors, ensure equivalent coverage and durability.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/ecs-controls.html#ecs-9
- https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html#specify-log-config
- https://docs.aws.amazon.com/config/latest/developerguide/ecs-task-definition-log-configuration.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ecs_task_definitions_logging_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks