1 Answer
- Newest
- Most votes
- Most comments
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.
Relevant content
- Accepted Answerasked 7 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
I checked container log didn't find any. Metrics for CPU usage is high on issue time.