- 최신
- 최다 투표
- 가장 많은 댓글
According to AWS support, this is a known limitation of App Runner (requests running longer than 30 seconds result in HTTP 503), and is scheduled to be addressed in a future update. No ETA given unfortunately.
I don't think we cut hard the connectivity but we do throttle the CPU down when there is no active requests to the instance. See this thread.
How/where do you issue the
curl
command? Do you schedule it from the outside?Hi. I issue the
curl
command from outside, from a normal internet-connected host, outside of AWS. For me this strongly feels like a 30 second timeout enforced by either load balancer or envoy proxy.I investigated this further and added a route in the micro service that just sleeps for a specified amount of seconds and then returns an HTTP 200 response, to eliminate any other factors in the application.
$ curl -v https://.../sleep?seconds=31
GET /sleep?seconds=31 HTTP/1.1 Host: <redcated>.eu-west-1.awsapprunner.com User-Agent: curl/7.64.1 Accept: /
< HTTP/1.1 503 Service Unavailable < content-length: 95 < content-type: text/plain < date: Wed, 29 Dec 2021 13:19:47 GMT < server: envoy < connection: close
Sleeping for a shorter time (e.g. 29 seconds or less) works fine.
I will try approaching AWS support with this. Thanks for the pointer though!
Is this documented somewhere?
The timeout per request is currently 120 sec.