ASP.NET Core Web API Serverless Application

This project shows how to run an ASP.NET Core Web API project as an AWS Lambda exposed through Amazon API Gateway. The NuGet package Amazon.Lambda.AspNetCoreServer contains a Lambda function that is used to translate requests from API Gateway into the ASP.NET Core framework and then the responses from ASP.NET Core back to API Gateway.

For more information about how the Amazon.Lambda.AspNetCoreServer package works and how to extend its behavior view its README file in GitHub.

Configuring for API Gateway HTTP API

API Gateway supports the original REST API and the new HTTP API. In addition HTTP API supports 2 different payload formats. When using the 2.0 format the base class of LambdaEntryPoint must be Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction. For the 1.0 payload format the base class is the same as REST API which is Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction. Note: when using the AWS::Serverless::Function CloudFormation resource with an event type of HttpApi the default payload format is 2.0 so the base class of LambdaEntryPoint must be Amazon.Lambda.AspNetCoreServer.APIGatewayHttpApiV2ProxyFunction.

Configuring for Application Load Balancer

To configure this project to handle requests from an Application Load Balancer instead of API Gateway change the base class of LambdaEntryPoint from Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction to Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction.

Project Files

• serverless.template - an AWS CloudFormation Serverless Application Model template file for declaring your Serverless functions and other AWS resources
• aws-lambda-tools-defaults.json - default argument settings for use with Visual Studio and command line deployment tools for AWS
• LambdaEntryPoint.cs - class that derives from Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction. The code in this file bootstraps the ASP.NET Core hosting framework. The Lambda function is defined in the base class. Change the base class to Amazon.Lambda.AspNetCoreServer.ApplicationLoadBalancerFunction when using an Application Load Balancer.
• LocalEntryPoint.cs - for local development this contains the executable Main function which bootstraps the ASP.NET Core hosting framework with Kestrel, as for typical ASP.NET Core applications.
• Startup.cs - usual ASP.NET Core Startup class used to configure the services ASP.NET Core will use.
• appsettings.json - used for local development.
• Controllers\ValuesController - example Web API controller

You may also have a test project depending on the options selected.

Here are some steps to follow from to get started with the Terraform:

The role (production.lambda-execute.role) and policies (below) for Lambda execution and trace logging need to be setup ahead of time.

Lambda execution (AWSLambdaBasicExecutionRole)

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "logs:CreateLogGroup",
                "logs:CreateLogStream",
                "logs:PutLogEvents"
            ],
            "Resource": "*"
        }
    ]
}

Trace logging (AWSLambdaTracerAccessExecutionPolicy)

{
    "Version": "2012-10-17",
    "Statement": {
        "Effect": "Allow",
        "Action": [
            "xray:PutTraceSegments",
            "xray:PutTelemetryRecords"
        ],
        "Resource": [
            "*"
        ]
    }
}

To deploy your function to AWS Lambda, run the below commands from the /hosting/src folder.

    terraform init
    terraform validate
    terraform plan
    terraform apply
    terraform destroy

Here are some steps to follow from Visual Studio:

To deploy your Serverless application, right click the project in Solution Explorer and select Publish to AWS Lambda.

To view your deployed application open the Stack View window by double-clicking the stack name shown beneath the AWS CloudFormation node in the AWS Explorer tree. The Stack View also displays the root URL to your published application.

Here are some steps to follow to get started from the command line:

Once you have edited your template and code you can deploy your application using the Amazon.Lambda.Tools Global Tool from the command line.

Install Amazon.Lambda.Tools Global Tools if not already installed.

    dotnet tool install -g Amazon.Lambda.Tools

If already installed check if new version is available.

    dotnet tool update -g Amazon.Lambda.Tools

Execute unit tests

    cd "webApiDotnet.Function/test"
    dotnet test

Deploy application

    cd "webApiDotnet.Function/src"
    dotnet lambda deploy-serverless