misconfig.cloud
Example task — all resources and results below are demo data.Request workspace access
Tasks/DEMO-1042

DEMO-1042 · PRODUCTION · EU-CENTRAL-1

ECS health checks started failing after this morning's deployment

Requested by Elena Marinova · 09:14 UTC

Plan ready
Investigate
Prepare plan
3Grant permission
4Approve
5Execute
6Verify

What Misconfig found

Evidence collected with the connected read role

Health-check path no longer matches the application.

Deployment revision 184 completed at 08:51 UTC. The new container reports ready on /ready, while the target group still checks /health and receives HTTP 404.

EvidenceObserved valueTime
ECS service events3 tasks reached RUNNING09:09
Target health3 unhealthy · HTTP 40409:10
Task definitionapi:184 · /ready09:10
Target groupHealthCheckPath=/health09:11

Proposed change

Plan version 3 · digest sha256:89fd…7a20

arn:aws:elasticloadbalancing:eu-central-1:111122223333:targetgroup/api/73e2f1
Before/healthAfter/ready
Operation
ModifyTargetGroup
Expected impact
New checks use the application's readiness endpoint. No task restart.
Stop condition
Stop if the target group or task definition changed after this plan.
Verification
All 3 targets healthy for 5 consecutive checks.
Recovery
Restore /health only if revision 184 is rolled back and the old endpoint is confirmed.