On Fargate, treat the task definition as the contract: the container port Node listens on, CPU/memory, and env must match what the process actually binds. Prefer a multi-stage image that copies only production node_modules and app code into a slim runtime, run as non-root, and inject secrets at task/runtime rather than baking them into ECR layers. Point the ALB or service health check at a cheap liveness route; keep datastore depth on readiness so a short DB blip does not thrash task replacements.
Ops prove-out after the first healthy revision: confirm running tasks, hit once through the public service URL and once to a task private IP:port, and compare status codes plus Host / X-Forwarded-* behaviour against localhost assumptions. If the target group flaps, verify security groups, the mapped container port, and whether the health path still blocks on a dependency that is cold at start.