Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 4.31 KB

lambda-dotnet-create-deployment-package-toolkit.md

File metadata and controls

55 lines (39 loc) · 4.31 KB

AWS Toolkit for Visual Studio

You can build .NET-based Lambda applications using the Lambda plugin to the AWS Toolkit for Visual Studio. The plugin is available as part of a Nuget package.

Step 1: Create and Build a Project

  1. Launch Microsoft Visual Studio and choose New project.

    1. From the File menu, choose New, and then choose Project.

    2. In the New Project window, choose AWS Lambda Project (.NET Core) and then choose OK.

    3. In the Select Blueprint window, you will be presented with the option of selecting from a list of sample applications that will provide you with sample code to get started with creating a .NET-based Lambda application.

    4. To create a Lambda application from scratch, choose Blank Function and then choose Finish.

  2. Examine the aws-lambda-tools-defaults.json file, which is created as part of your project. You can set the options in this file, which is read by the Lambda tooling by default. The project templates created in Visual Studio set many of these fields with default values. Note the following fields:

    • profile: The IAM role required for your Lambda function's execution. If you have not yet created an execution role, do the following:

      1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

      2. Follow the steps in Creating a Role to Delegate Permissions to an AWS Service in the IAM User Guide to create an IAM role (execution role). As you follow the steps to create a role, note the following:

        • In Role Name, use a name that is unique within your AWS account.
        • In Select Role Type, choose AWS Service Roles, and then choose a service role that grants that service permissions to assume the role.
        • In Attach Policy, choose a permissions policy that is suitable to execute your Lambda function.

    • function-handler: This is where the function handler is specified, which is why you don't have to set it in the wizard. However, whenever you rename the Assembly, Namespace, Class or Function in your function code, you will need to update the corresponding fields in the aws-lambda-tools-defaults.json file.

      {
  "profile":"iam-execution-profile"",
  "region" : "region",
  "configuration" : "Release",
  "framework" : "netcoreapp2.1",
  "function-runtime":"dotnetcore2.1",
  "function-memory-size" : 256,
  "function-timeout" : 30,
  "function-handler" : "Assembly::Namespace.Class::Function" 
}

  3. Open the Function.cs file. You will be provided with a template to implement your Lambda function handler code.
    [Image NOT FOUND]

  4. Once you have written the code that represents your Lambda function, you can upload it by right-clicking the Project node in your application and then choosing Publish to AWS Lambda.

  5. In the Upload Lambda Function window, type a name for the function or select a previously published function to republish. Then choose Next

  6. In the Advanced Function Details window, do the following:

    • Specify the Role Name:, the IAM role mentioned previously.
    • (Optional) In Environment:: specify any environment variables you wish to use. For more information, see AWS Lambda Environment Variables.
    • (Optional) Specify the Memory (MB): or Timeout (Secs): configurations.
    • (Optional) Specify any VPC: configurations if your Lambda function needs to access resources running inside a VPC. For more information, see Configuring a Lambda Function to Access Resources in an Amazon VPC.
    • Choose Next and then choose Upload to deploy your application.

For more information, see Deploying an AWS Lambda Project with the .NET Core CLI.