- Newest
- Most votes
- Most comments
I know this is an old question, but I was having a similar problem and thought I would provide my experience in case it would help anyone else (for the record, I think the answer of "Make your application faster" is not helpful at all). In my case, we are hosting a website with Fargate and fronting it with CloudFront origins. Long running APIs would timeout and return a 504 to the client due to the CloudFront request timeout setting on the origin. By default, the max you can set this timeout is 60 seconds, but you can do a service limit request and have it bumped up to 180 seconds. That is their current hard limit and they won't go higher than that. Once I did that and updated my CloudFront origin, my 504 errors went away.
Request / Response taking longer than a minute is already in very bad standing.
Make your application faster or redesign it to be batched / async?
Relevant content
- Accepted Answerasked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
It's machine learning service so it takes long. We can't make our application faster than this.
Websockets is another legitimate use case where you don't want the connection to be automatically timed out. Anyone figure out where the timeout is set?