AWS API Gateway: forcing a 200OK response, while passing data to backend (python39 lambda) for handling?

Question

Hi all,

I'm getting stuck on a problem of how to properly handle a POST request from a 3rd party (webhook) who expects an immediate 200OK response upon receiving the message or it resends.

I have handled issues like this in the past with the inclusion of a lambda that the API points to pushing the message to a que system (SQS), and returning 200OK once that is complete. While w/e backend processes needed to run, can handle their business in peace. Is there no way, at the API gateway level, or directly in the lambda, to force a status response without waiting for the lambda to return a response when it's completed it's run? Is this just the standard to decouple the response message from the backend?

Accepted Answer

You can consider using the following design patterns:
1. Use [AWS Integration target](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_apigateway-readme.html#integration-targets) for API Gateway, so that it will send messages directly to an SQS queue and have Lambda function to be triggered from that queue for message processing. See [Amazon API Gateway to SQS to Lambda pattern](https://serverlessland.com/patterns/apigw-http-sqs-lambda-cdk), for example.
2. You can leverage Lambda [Asynchronous invocation](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html) capability with API Gateway's Lambda Integration as described here: [Set up asynchronous invocation of the backend Lambda function](https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-integration-async.html).

The difference between option 1 and 2 is that SQS queue for the option 2 is managed internally by Lambda runtime and you have less control over its configuration.

That way, API Gateway will respond to the caller without waiting for Lambda to complete its execution.

AWS API Gateway: forcing a 200OK response, while passing data to backend (python39 lambda) for handling?

相關內容