Skip to content

Latest commit

 

History

History

BatchProcessing

README.md

Powertools for AWS Lambda (.NET) - Batch Processing Example

This project contains examples of a Lambda function using the batch processing module of Powertools for AWS Lambda (.NET). For more information on this module, please refer to the documentation. documentation.

  • src - Code for the application's Lambda function.
  • events - Invocation events that you can use to invoke the function.
  • test - Tests for the application code.
  • template.yaml - A template that defines the application's AWS resources.

The application uses several AWS resources, including a Lambda function.

These resources are defined in the template.yaml file in this project. You can update the template to add AWS resources through the same deployment process that updates your application code.

Three different examples and SAM deployments are included, covering each of the batch sources:

  • SQS - SQS batch processing
  • Kinesis Streams - Kinesis Streams batch processing
  • DynamoDB Streams - DynamoDB Streams batch processing

Deploy the sample application

The AWS SAM CLI is an extension of the AWS Command Line Interface (AWS CLI) that adds functionality for building and testing Lambda applications. It uses Docker to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.

To use the AWS SAM CLI, you need the following tools.

You will need the following for local testing.

To build and deploy your application for the first time, run the following in your shell. Make sure the template.yaml file is in your current directory:

sam build
sam deploy --guided

The first command will build a docker image from a Dockerfile and then copy the source of your application inside the Docker image. The second command will package and deploy your application to AWS, with a series of prompts:

  • Stack Name: The name of the stack to deploy to CloudFormation. This should be unique to your account and region, and a good starting point would be something matching your project name.
  • AWS Region: The AWS region you want to deploy your app to.
  • Confirm changes before deploy: If set to yes, any change sets will be shown to you before execution for manual review. If set to no, the AWS SAM CLI will automatically deploy application changes.
  • Allow SAM CLI IAM role creation: Many AWS SAM templates, including this example, create AWS IAM roles required for the AWS Lambda function(s) included to access AWS services. By default, these are scoped down to minimum required permissions. To deploy an AWS CloudFormation stack which creates or modifies IAM roles, the CAPABILITY_IAM value for capabilities must be provided. If permission isn't provided through this prompt, to deploy this example you must explicitly pass --capabilities CAPABILITY_IAM to the sam deploy command.
  • Save arguments to samconfig.toml: If set to yes, your choices will be saved to a configuration file inside the project, so that in the future you can just re-run sam deploy without parameters to deploy changes to your application.

Run tests

Tests are defined in the test folder in this project.

$ dotnet test test/HelloWorld.Test

Cleanup

To delete the sample application that you created, use the AWS SAM CLI. Assuming you used your project name for the stack name, you can run the following:

$ sam delete