This library helps you create a console application that hosts your AWS Lambda function so that you can easily debug its execution. This is important especially when working on a distributed system composed by several services and applications.

Note: this works only with AWS Lambda functions based on the dotnetcore2.0 runtime.

The library creates a small ASP.NET Core application that listens to a port and forwards every call to an web handler whose responsibility is to deserialize the incoming request's body to a well known type, execute the function handler, and deserialize the response, if any.

The best way to run your Lambda functions locally is to create a new console application in your solution and add a reference to the project containing the function.

Once you have added the EMG.Lambda.LocalRunner package to your application, you can simply replace your Main function with something similar to the following snippet.

LambdaRunner.Create()
            .Receives<string>()
            .Returns<string>()
            .UsesFunction<Function>((function, input, context) => function.FunctionHandler(input, context))
            .Build()
            .RunAsync()
            .Wait();

If your function returns a Task<T>, you can use the UsesAsyncFunction method.

LambdaRunner.Create()
            .Receives<string>()
            .Returns<string>()
            .UsesAsyncFunction<Function>((function, input, context) => function.FunctionHandlerAsync(input, context))
            .Build()
            .RunAsync()
            .Wait();

If your function has no return type, you skip the Returns<T>() and use UsesFunctionWithNoResult or UsesAsyncFunctionWithNoResult

LambdaRunner.Create()
            .Receives<string>()
            .UsesFunctionWithNoResult<Function>((function, input, context) => function.FunctionHandler(input, context))
            .Build()
            .RunAsync()
            .Wait();

LambdaRunner.Create()
            .Receives<string>()
            .UsesAsyncFunctionWithNoResult<Function>((function, input, context) => function.FunctionHandlerAsync(input, context))
            .Build()
            .RunAsync()
            .Wait();

Here there is a tutorial that helps you creating your first local runner application.

When constructing your runner, you can customize it by providing two optional parameters: the port to bind and the serializer to use.

If you plan to locally run more than one Lambda function, you need to use bind different ports. This can be easily done by using the UsePort(int port) method. If omitted, the default port 5000 will be used.

LambdaRunner.Create().UsePort(5001) ...

You can use the WithResponseContentType(string contentType) method to set a value that will be returned in the Content-Type header. If omitted the default application/json will be used.

LambdaRunner.Create()
            .Receives<string>()
            .Returns<Foo>()
            .WithResponseContentType("application/xml")
            .UsesFunction<Function>((function, input, context) => function.FunctionHandler(input, context))
            .Build()

If you need to use a different serialization strategy, you can specify the serializer while building the runner by using the UseSerializer<T>(Func<T> factory). For consistency with the AWS Lambda SDK for .NET, the custom serializer you use must implement the ILambdaSerializer interface. If omitted, the default Amazon.Lambda.Serialization.Json.JsonSerializer will be used.

LambdaRunner.Create().UseSerializer(() => new MyCustomSerializer()) ...

C# 7.1 introduced the support to async/await directly in the Main method of a console application.

Once your console application has an Async Main method, you can rewrite your console application so that it looks like the following snippet

static async Task Main(string[] args)
{
    await LambdaRunner.Create()
                        .UsePort(5001)
                        .Receives<string>()
                        .UsesAsyncFunctionWithNoResult<Function>((function, input, context) => function.FunctionHandlerAsync(input, context))
                        .Build()
                        .RunAsync();
}

By default, features introduced in minor versions of the compilers are turned off. To enable these features, you can simply modify your project file.

Adding the following setting in your project file will enable the latest available feature.

<LangVersion>latest</LangVersion>

Please, make sure to have the latest version of the C# compiler installed on your machine or any build server you might be using.

This project uses Cake as a build engine.

If you would like to build Nybus locally, just execute the build.cake script.

You can do it by using the .NET tool created by CAKE authors and use it to execute the build script.

dotnet tool install -g Cake.Tool
dotnet cake