Benchmark: Elastic Container Service
Overview
This section contains recommendations for configuring ECS resources and options.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select Elastic Container Service.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_ecsSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.foundational_security_ecs --shareControls
- 1 Amazon ECS task definitions should have secure networking modes and user definitions
- 2 Amazon ECS services should not have public IP addresses assigned to them automatically
- 3 ECS task definitions should not share the host's process namespace
- 4 ECS containers should run as non-privileged
- 5 ECS containers should be limited to read-only access to root filesystems
- 8 Secrets should not be passed as container environment variables
- 9 ECS task definitions should have a logging configuration
- 10 Fargate services should run on the latest Fargate platform version
- 12 ECS clusters should have Container Insights enabled