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.

主题

无服务器计算前端 Web 和移动网络和内容交付

标签

无服务器 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

相关内容