Building AWS Lambda Functions with C# and .NET/

...

/

Anatomy of an AWS Lambda Application

Anatomy of an AWS Lambda Application

Learn the structure of an AWS Lambda function.

We'll cover the following...

In this lesson, we’ll take a look at the basic structure shared by all AWS Lambda applications using the following playground.

{
  "Information": [
    "This file provides default values for the deployment wizard inside Visual Studio and the AWS Lambda commands added to the .NET Core CLI.",
    "To learn more about the Lambda commands with the .NET Core CLI execute the following command at the command line in the project root directory.",
    "dotnet lambda help",
    "All the command line options for the Lambda command can be specified in this file."
  ],
  "profile": "",
  "region": "",
  "configuration": "Release",
  "function-architecture": "x86_64",
  "function-runtime": "dotnet6",
  "function-memory-size": 256,
  "function-timeout": 30,
  "function-handler": "LambdaApp::LambdaApp.Function::FunctionHandler"
}
Basic AWS Lambda application

This is a very simple AWS Lambda application with a single function. The function accepts any arbitrary text as its input, converts it to an all-uppercase version, and returns it to the sender. Two main components make the functions work:

  • JSON configuration

  • Function handler

Let’s examine these.

JSON configuration

In the example, the JSON configuration is represented by the aws-lambda-tools-defaults.json file. This is the default name of the configuration file that is created when an AWS Lambda project is initialized. You can use a file with an alternative name, as long as it’s JSON.

If we open the file, we’ll see that it consists of the following fields:

    ...