Function as a Service

C# and AWS Lambdas, Part 6 – .NET 5 inside a Container inside a Lambda

A few months ago AWS released a feature allowing Lambdas to run container images, for larger applications this is easier to work with than a zip file or set of layers, it also lets you move your already containerized apps to Lambda with a small effort. This post shows how to get .NET 5 “Hello World” application running in this manner.

Mar 17, 2021 # AWS, Container, Docker, dotNET 5, AWS Lambda, Function as a Service

C# and AWS Lambdas, Part 5 – Updating the Zip in S3 and Updating the Running Lambda, with Pulumi IaC

This post pulls together a few threads I’ve been working on - the creation of Lambda to run .NET, storing the zip in S3, and updating the .NET Lambda when the zip in S3 is updated. This one took quite a while to put together - the permissions, roles, and policies were not obvious and I hope it will be of help to you.

Mar 10, 2021 # dotNet Core 3.1, AWS, dotNet, IaC, AWS Lambda, Pulumi, S3, Function as a Service

C# and AWS Lambdas, Part 4 – Storing the Zip in S3, Setup with Pulumi IaC

In the previous post, I showed how to use Pulumi to create a Lambda, API gateway and upload a zip of Web API application directly to the Lambda.

In the post I’m going to use S3 to store the zip of a simple .NET application (not a Web API app) and point the Lambda at it, bringing all the resources up using Pulumi. One drawback of using S3 to store the zip for a Lambda is that when you update the zip in S3, AWS doesn’t deploy the new zip to the Lambda, but I will show a way of handling that in the next blog post.

Mar 3, 2021 # dotNet Core 3.1, AWS, dotNet, IaC, AWS Lambda, Pulumi, Function as a Service

C# and AWS Lambdas, Part 3 – Pulumi IaC for Web API and an API Gateway

In this the third in a series of posts on using .NET in AWS Lambdas I build on the previous post where I connected a Http Gateway to a Lambda running a Web API application. In that post I built the infrastructure by hand, i.e. via the GUI, pointing and clicking.

In this post, I will show how to build everything with Pulumi.

Feb 25, 2021 # dotNet Core 3.1, AWS, dotNet, IaC, AWS Lambda, Pulumi, Function as a Service

C# and AWS Lambdas, Part 2 - Web API and an API Gateway

In the previous post I created a Lambda that executed a C# console application. In this post, I walk through creating a .NET Core 3.1 Web API application inside a Lambda and making it reachable from the web, just like a normal Web API application.

Feb 18, 2021 # dotNet Core 3.1, AWS, dotNet, AWS Lambda, Function as a Service

C# and AWS Lambdas, Part 1 - Hello World

First in a series of posts on using .NET with AWS Lambdas. It will start with the simplest example that converts a lowercase string to an uppercase string, but by the end, you will be running a .NET Web API powered by Lambda, fronted by an API gateway where all the infrastructure is set up by Pulumi - this will take a few posts over the next while.

Feb 3, 2021 # dotNet Core 3.1, AWS, dotNet, AWS Lambda, Function as a Service

Indexing the Works of Shakespeare in Elasticsearch – Part 3, Sending the Lines to Kinesis

In this, the third part of the series, I show how to read from the Shakespeare CSV file where each row represents a line from a play, (download here), and send these lines to Kinesis. The lambda in AWS will pick up the lines from Kinesis and forward them to Elasticsearch for indexing.

Nov 25, 2020 # AWS, Elasticsearch, Kinesis, AWS Lambda, Function as a Service

Indexing the Works of Shakespeare in Elasticsearch - Part 2, Bulk Indexing

With Elasticsearch, indexing data in bulk is a more reliable and scalable approach than indexing a high volume of documents one at time. Here is how to achieve this with AWS Kinesis and a Lambda.

Nov 24, 2020 # AWS, Elasticsearch, Kinesis, AWS Lambda, Function as a Service

Indexing the Works of Shakespeare in Elasticsearch - Part 1, Infrastructure as Code

Part one of a four-parter where I’m going to show how to index the complete works of Shakespeare in Elasticsearch. This first part will set up the infrastructure on AWS. The second will go through the lambda that bulk loads data into Elasticsearch. The third will show how to, in Node.js, create the index on the Elasticsearch domain, read the works of Shakespeare from CSV and send to Kinesis, and the fourth will put a .NET 5 Web Api in front of the Elasticsearch cluster.