1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
If you have ALB logging enabled then I would use the logs to find which container is returning the 504
Then dig deeper into the application. It may be the container is overloaded and out of available http connections at that time or not enough threads.
You’d need to look at tuning your app.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
I checked container log didn't find any. Metrics for CPU usage is high on issue time.