dotNet6

Here’s a quick example using IOptions with .NET 6 API Endpoints.

If you are using IAM auth with Lambda Function URLs, and you want to call the function using HttpClient from a .NET application, you need to sign the request. Read on to see how.

Even though Lambda functions are “serverless”, and even though there is no guarantee how long a function will remain “warm” for, you might still get good use out of a memory cache.

Here are two ways to page through files in an S3 bucket.

Following on from my previous post on using a memory cache, here I show how to use a distributed memory cache with Redis.

I have used the Microsoft memory cache many times in the past, but didn’t know how to use it with .NET 6 endpoints, so here is a blog post that should save you a little time if you haven’t done it before.

When a Lambda function is connected to a VPC, the function can no longer access the internet. One way to resolve this is to use a NAT gateway, read on to see how.

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.