API Gateway returns 503 after one second - no Lambda request id

During high load I get the following trace roughly one second after the authorizer of my API Gateway was successfully called:

"(a03fe070-b6d0-4e4c-bea1-9cc77f3f0abc) Lambda invocation failed with status: 503. Lambda request id: N/A"

Any hints what might have failed? I don't see any other traces (in called/not-called Lambda), throttling events or anything like this. Number of calls, though rather high, seems to be within the quotas.

Note that 99.9% of all calls succeed.

주제

서버리스 컴퓨팅 프론트엔드 웹 및 모바일 네트워킹 및 콘텐츠 전송

태그

서버리스 AWS Lambda 아마존 API 게이트웨이 서비스 할당량

언어

English

Dunken

질문됨 2달 전304회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

A 503 error code indicates a problem with the backend integration, where the API Gateway API cannot receive a response from the backend server. This error may occur in situation when the backend server is overwhelmed by excessive traffic and cannot handle new client requests.

AWS-User-8193398

답변함 2달 전

전문가

Giovanni Lauria

검토됨 2달 전

Dunken
2달 전
This I understand but I would like to figure out what exactly was overwhelmed... I don't see any traces or metrics which would point me to any resource.

API Gateway returns 503 after one second - no Lambda request id

관련 콘텐츠