awslabs / awslabs/aws-lambda-cpp

LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint

Open
#26 16 comments 0 reactions 0 assignees View on GitHub
libcurl
Dominant language
C++
Stars
465
Forks
98
Avg merge
12h 47m
Merged PRs (30d)
3

Description

Hi guys!

I just writing some lambdas in c++ using the aws-lambda-cpp

i checking my log and i have this Error in my log:

>
[ERROR] [1553201323958] LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint

do you know if this is normal? because i check and debug my code but i don't found nothing.

what my lambda do is extract the body from SQS request, and make a slack post with the message.

for that i use curl and have the ssl disable

other thing is i dont see a print message that i have in the main after the

```
invocation_response handler(invocation_request const &req) {
return invocation_response::success();
}

```
this is my main:

```
int main() {
//use AWS namespace and libs
using namespace Aws;
//set the log for the sdk
SDKOptions options;
//init AWS API
InitAPI(options);
{
auto handler_function = [](aws::lambda_runtime::invocation_request const &req) {
return handler(req);
};
run_handler(handler_function);
}
// shutdown the aws api
std::cout << "ShutdownAPI api" << "\n";
ShutdownAPI(options);

std::cout << "exit" << "\n";

//exit
return 0;
}
```

i dont see the Shutdown and exit print in the cloud-watch log

so the question
the ShutdownAPI(options); and the return 0 is never called?

thank you!!!

Contributor guide

Open the contributing guide

Research direction

Start with the reported LAMBDA_RUNTIME log and the main function's run_handler entry point, then trace whether handler(req) returns and where ShutdownAPI is reached. Confirm the expected lifecycle from the runtime behavior and document what should be visible in CloudWatch; done means the endpoint message and missing prints are explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, cpp
Domain
backend, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.