1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Your setup looks almost correct. However, you need to set your Target Group to point to port 4000 instead of 443. Otherwise it will be unable to establish a connection with your Fargate task.
In addition, you will want to confirm your Fargate security group allows incoming traffic from the Load Balancer, and you'll want to make sure your health check is configured and it shows healthy targets.
The errors you're receiving mean:
- 503 Service Temporarily Unavailable -- Your Fargate task(s) are not running, and there are no targets registered to the load balancer.
- 504 Gateway Time-out -- There is at least one target registered to the load balancer, but it's not responding on the configured port.
The reason it's flipping between 503 and 504 is because your Target Group cannot reach your Fargate task, so the health check is failing, and the task is getting restarted over and over.
If you clear up the connectivity between the Target Group and the Fargate task, this will probably solve the problem.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
It looks like the setup should be able to work as long as the target group is setup to forward traffic to the relevant host. Have you already checked that the host security group or subnet network ACL allow that traffic from your load balancer?
Are any targets showing up in the console for the group? And are the health checks showing as successful?