dotNet6

This post shows how easy it is to create a simple Lambda function written in C#.

In a previous post, I showed how to use a VPC Endpoint to give a Lambda function (which is connected to the VPC) access to Secrets Manager. In this post, I will show how to use a NAT Gateway to give a Lambda function access to Secrets Manager and the internet.

Calling one Lambda function from another is something you’ll occasionally need to do. If you are using Lambda function URLs it is a simple HTTP request. But you can also use the AWS Lambda SDK to invoke the other function.

If you are getting this - “Error converting the Lambda event JSON payload to type System.String”, you might need to serialize the payload you are sending. Read on to see how.

When a Lambda function is connected to a VPC, accessing the Secrets Manager becomes more complicated because the function no longer has internet access. One way to resolve this is to use a VPC endpoint.

Following on from a post earlier this month on lambdas, here are some examples that are a little more complicated.

It is easy to debug an AWS Lambda function locally with Visual Studio Code, all you need to do is install one tool and make one change to the launch.json file. Read on to see how.

In an earlier post I showed how to use a .NET 6 Lambda function to retrieve a secret from Secrets Manager synchronously, but it is also easy to do this asynchronously.

There are many ways to write and use lambdas in C# that. In this post I give an overview of what they are, examples of how to write them with detailed comments, and how to use them.

Even when using Polly retries, there are times when you just want to give. The cancellation token is a great way to do this.