I have a simple QR Code scanner that sends an API request to a server (it is factory made like that) I want this QR code send the data to a lambda that I have on AWS through an API gateway.
The QR code scanner sends the reading result in pure plain text by POST method but my post api gateway only accepts json, I need it to accept pain text and pass it to my lambda.

I have a (public) API Gateway that uses a custom Lambda authorizer that we need to both (a) authorize custom access token and (b) JWTs.

I’ve recently migrated a local python script to lambda via aws cdk. It collects data from an public api endpoint. On my local machine this function works 100% of the time when it comes to status codes and responses from the api.

I’m using Bedrock/Claude to stream output to a mobile app using Sockets.
I’m aware that this error occurs when we use post_to_connection within $connect, which I am not doing.
It also is known to happen when the ConnectionID changes unexpectedly.
And I know the max execution time for a Lambda function is 29 seconds. Mine executes for no more than 5-8 seconds, even when it makes this error.

I have been at this for hours trying to resolve my issue and I cannot for the life of me.

I’m working on an AWS lambda code with an API request as its trigger.
I want to extend the timeout limit of my API Gateway beyond 29 seconds, which, as I understand, became possible quite recently, but I don’t really understand the way to do it:

I have 10 lambdas running and all of them are timing out even before executing the first log in the handler. So the timeout is not caused by anything in the code logic.

I have 10 lambdas running and all of them are timing out even before executing the first log in the handler. So the timeout is not caused by anything in the code logic.

I am currently working with GitLab webhook to trigger a Lambda function through AWS API Gateway, which will trigger a CI pipeline in another repository. My question is whether it is possible to validate the value of the X-Gitlab-Token in header at the mapping template level and if the token is incorrect just don’t pass the request to Lambda. It should be done without invoking the any other Lambda function for validation

I am trying to set my login and register lambda functions. Both of them are setted as POST with the OPTION CORS methods. Both of them have same configurations. Login is working without problem but register is giving me this error.