2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
I found the root cause of the 503 errors. VPC links require to use private subnets. If I put public subnets along with the private subnets it returns 503 errors most of the time. After removing public subnets from the VPC Link it is fixed.
répondu il y a 2 ans
0
Hello,
I believe the above logs is from applicaiton load balancer access logs.
Check your Application Load Balancer access logs. Confirm that there is an elb_status_code = 503 in the logs. If you see 503 errors in any of these places, the error is generated by your Application Load Balancer.
- Please verify the hat the target group has registered targets
- Check that the traffic port and the health check port are the same.
- Also check all the services are running in the container
- It can also happen if you have the correct port configured in the health check settings, but the wrong port configured for sending actual traffic to the container.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an