AWS Lambda .NET Class Library
Learn the structure of a basic AWS Lambda .NET project.
We'll cover the following...
In this lesson, we’ll take a detailed look at the .NET SDK for AWS Lambda and see how the most basic AWS Lambda application project is structured. The example we’ll use is in 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"
}The project in this playground represents a simple AWS Lambda function that accepts a request from ELB and returns an HTML response. We don’t need to know what ELB is. With Lambda Test Tool, we don’t even need it to invoke the function. We chose this project type for two reasons:
It’s an AWS Lambda project template.
It’s the simplest project template that allows us to use more complex object input rather than very basic string input.
If we want to execute this function, we can click the “Run” button in the playground. Once the application is loaded, we can select “Application Load Balancer” as the example request to populate the “Function Input” field with the appropriate data. Then we can click the “Execute ...
Create a free account to view this lesson.
By signing up, you agree to Educative's Terms of Service and Privacy Policy