Ensure ECS tasks do not have secrets in environment variables
Secrets should not be passed as plaintext environment variables in task definitions.
Security Impact
Environment variables are visible in task definitions and can be exposed in logs.
How to Remediate
Use secrets from AWS Secrets Manager or Parameter Store with the 'secrets' field in container definitions.
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, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ecs-13
- Service
- Elastic Container Service (ECS)
- Category
- Credential Management
- Severity
- HIGH
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