AWS Lambda

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.

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.

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.

.NET Lambda functions can get secrets from AWS Secrets Manager, but you need to grant the Lambda function permission to access the secret. Read on to find out how.

Querying an RDS SQL Server from Lambda is a great option for .NET applications. In this post you see how to create all the infrastructure, seed the database, deploy a .NET 6 Web API application, and connect the VPCs.

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.

Running .NET 6 Lambda serverless applications on ARM64 needs only one small change from the default template.