Lambda Destinations

Service Name:	Lambda
ARN Format:	`{region}:{account}:function:{name and qualifier}`
Style:	Request/Response
Actions (required Permissions):	`lambda:InvokeFunction`
Payload Format:	JSON object with array of request packet objects

Using an AWS Lambda function as a destination allows great flexibility and capability, and is a great option when generating replies to inbound packets is necessary (StepFunctions is another). Lambda a good choice for implementing protocols with request/response semantics and provides a familiar development experience.

Technical Details

Proxylity's integration with Lambda uses the lambda:InvokeFunction API to deliver batches packets to your function. Destination functions can be implemented in any language supported by Lambda, including Node.js, Python, Java, Go and .NET.

The payload provided to the Lambda function is a JSON object with a property Messages containing an array of request packet objects. The response from the function is used to generate replies, and contains a Replies property containing an array of one or more response packet objects. Response packets are matched to the request packets using the Tag property. If no replies are needed or appropriate, return an empty array in Replies.

Getting Started with .NET

Proxylity provides an SDK and project templates to make developing Lambda destinations easier for .NET developers:

SDK: Proxylity.UdpGateway.LambdaSdk - Provides typed models and helper methods for working with UDP Gateway packets
Templates: Proxylity.Templates - Contains dotnet new templates for quick project setup

Install the templates and create a new Lambda function:

dotnet new install Proxylity.Templates
dotnet new proxylity-udp -n MyUdpHandler

See Lambda destinations in action in our Packet Counter example, demonstrating request/response UDP packet handling.