http4k / org.http4k.serverless / AwsLambdaFunction
abstract class AwsLambdaFunction<Req :
Any
, Resp>
Name | Summary |
---|---|
<init> | AwsLambdaFunction(adapter: AwsHttpAdapter <Req, Resp>, appLoader: AppLoaderWithContexts ) |
Name | Summary |
---|---|
ApiGatewayV1LambdaFunction | This is the main entry point for lambda invocations using the V1 payload format. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApiGatewayV1LambdaFunction : AwsLambdaFunction < Map < String , Any >, Map < String , Any >>, RequestHandler< Map < String , Any >, Map < String , Any >> |
ApiGatewayV2LambdaFunction | This is the main entry point for lambda invocations using the V2 payload format. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApiGatewayV2LambdaFunction : AwsLambdaFunction < Map < String , Any >, Map < String , Any >>, RequestHandler< Map < String , Any >, Map < String , Any >> |
ApplicationLoadBalancerLambdaFunction | This is the main entry point for lambda invocations coming from an Application LoadBalancer. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class ApplicationLoadBalancerLambdaFunction : AwsLambdaFunction < Map < String , Any >, Map < String , Any >>, RequestHandler< Map < String , Any >, Map < String , Any >> |
InvocationLambdaFunction | This is the main entry point for lambda invocations using the direct invocations. It uses the local environment to instantiate the HttpHandler which can be used for further invocations.abstract class InvocationLambdaFunction : AwsLambdaFunction < InputStream , InputStream >, RequestStreamHandler |