AWS Lambda

See how to use AWS Step Functions to control the flow of a series of Lambda functions. In this example, the Lambda functions execute quickly, return a result, and trigger the next step.

.NET Lambda functions can be triggered when messages arrive in an SQS queue. There are a few steps to set this up, read on to see how.

If you invoke a Lambda function passing in value that deserializes to an enum and you are using the DefaultLambdaJsonSerializer it will fail. This post shows how to get around that problem in two ways.

If you invoke a Lambda function with a number represented as a string, and you are using the DefaultLambdaJsonSerializer it will fail. This post shows how to get around that problem in two ways.

Many people are worried about cold starts for .NET applications on AWS Lambda, but they are probably not as bad as you think - they are not that frequent, and they are not that slow.

Sometimes a Lambda function can’t deserialize the JSON it receives because the model is wrong or the JSON is not as expected. This post shows how to output the raw JSON to CloudWatch logs so you fix the problem.

Even though Native AOT on .NET 7 doesn’t support ASP.NET Core applications yet, you can use AWS Lambda functions with Native AOT to easily handle HTTP requests.

In two recent posts I showed how to warm up execution environments for your Lambda functions so you can avoid the cold start penalty when you have a burst of traffic. In this post I’ll show how to use Lambda versions and aliases to make this process easier.

If you run a full ASP.NET Web API application in AWS Lambda function, here is a way to warm up many execution environments ahead of time to reduce cold starts.

If you know that your Lambda function needs to handle bursts of activity at a predictable time, and you want to avoid the slower response of cold stars for that burst, you can force the Lambda service to warm up execution environments for you ahead of the burst.