ECS Cluster Missing Container Insights
Task and container metrics are not collected, so capacity problems only surface as failed tasks.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Container Insights on ECS cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- ECS Clusters on AWS
- The fix, by hand
- ECS → Clusters → the resource → Update cluster.
- Under Monitoring → Use Container Insights → Enable.
- (Optional) pick Enhanced Container Insights for per-container granularity at higher cost.
- Save. Metrics appear in CloudWatch → Container Insights within ~5 min.
- Container Insights adds a per-task-per-hour charge. Evaluate on production / prod-like clusters first; consider sampling on dev clusters.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1505- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.