- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I have found some links on 502 Bad gateway issues. Check if they apply to your case and see if they help. Please ignore if your case is different
https://aws.amazon.com/premiumsupport/knowledge-center/load-balancer-http-502-errors/
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-502-bad-gateway.html
what is your architecture? does it involve Application Load Balancers? if yes, do you have access logs enabled at ALB as well as have application logs to look at as to why the instances are sending HTTP 502? Here are the common things to look at for tshooting HTTP 502 with ALB.[1]
when it comes to AWS Premium Support Plans, having at least Business Support will gave you the options to initiate a live contact (chat or call). and having the right severity of the support case can speed up the process of having an engineer work on it.
[1] Troubleshoot your Application Load Balancers - HTTP 502: Bad gateway - https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html#http-502-issues
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata un anno fa
Hey, What is the issue i can try to help you, Can you give me full information about the issue