Function URLs

There may be times when you want to share information between Lambda functions, using a distributed memory cache will help you do this.

The mediator pattern is very helpful for keeping business logic out of your API endpoints. This post provides a simple example of this with the MediatR library.

With Lambda versions and aliases you can setup A/B testing for your functions. This example uses .NET 6 and Lambda Function URLs, but the same principles apply to other languages.

This is a simple Lambda function that uses a Function URL. This blog post will be referenced in more complicated examples.

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.

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.

Lambda Function URLs are a very easy way to make a Lambda function executable via an HTTPS request, but without a small change you might hit some CORS issues. Read on to see how to fix this.

Here are three very quick demos of using .NET 6 on AWS Lambda that you can have up and running in minutes.

Lambda Function URLs are a very easy way to make a Lambda function executable via an HTTPS request, they deploy in seconds, and can scale to your needs.