API Gateway integration random status 500

0

Hello

We're experiencing random errors 500 in the calls to our API for which we cannot figure out the source. The same request would more or less fail one out of each five times with this error: {"message": "Internal server error"}

In the logs we can see that everything is fine, the ECS container even handles the request properly but in the API Gateway logs we find this line:
Thu Nov 14 10:46:04 UTC 2019 : Execution failed due to configuration error: Not a valid protocol version: {}HTTP/1.1 204 No Content

We have the following setup:
API Gateway --> VPC Link --> NLB --> TargetGroup --> ECS

Querying directly the ECS service or the NLB as mentioned before works as expected, the responses are always the same expected result.

Is there anything we should take into account when integration API Gateway through a VPC link? I couldn't find any entry anywhere for the error "Not a valid protocol version" nor any hints on how to debug it.

Thanks!

Edited by: catchoom on Nov 14, 2019 3:38 AM

已提问 5 年前930 查看次数
1 回答
0

In the end, we solved the issue by placing an HTTP Proxy between the NLB and an ALB, which routes the requests to the desired ECS containers by hostname.

API Gateway --> VPC Link --> NLB --> NGINX --> ALB TargetGroup --> ECS

已回答 5 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则