What was built regarding the **Large Response Lambda Middleware** is a great all-in-one solution for one specific lambda use case: - API Gateway with Lambda Proxy Integration Although, while we at epilot use this pattern a lot, it's by no means the only way Lambda is used. The same 6MB response limit applies in all Lambda use cases. Just to give some examples that are not covered by this middleware: - Lambda function URLs - Lambda in Step Functions - Direct Invoke via Lambda API - API Gateway Lambda service integration - Lambda@Edge Since the 6MB limit applies anywhere, we could build and publish something more generic that works for all Lambda use cases (not just this one).