If you have target groups and it is saying unhealthy in health check then it will stall the first ever deployment process to on Install phase, so you have to de-register the instance or service connected to target group and then once the deployment is completed then you can register the service again in target groups and it will healthy if the targeted port is exposed or otherwise you will have to figure it out in logs. I used docker logs to check where things go wrong.. deployment was successful but my internal code was faulty.