F# for the Cloud worker This post will be the final post in the F# for the cloud worker series. There are of course many more things to cover in this space (F# and cloud), but this will be done a bit different than the approach has been in these posts. Despite the challenges with being a .NET newbie in a realm infested with C#, I like F# and I do want to use it more, including Cloud-based solutions.
F# for the Cloud worker In part 3 we started with some very simple AWS Lambda deployments. In this part we are going to continue on that path, using the AWS Serverless Application Model (AWS SAM). This is essentially an extension to AWS Cloudformation, the AWS service that provides infrastructure-as-code capabilities. With Cloudformaton one can write declarations how the infrastructure should look like in AWS as templates.
F# for the Cloud worker In part 2 we started to build a simple script to show information about virtual machines in AWS (EC2 instances). There was also a focus on developer workflow and work integrated with the editor and the F# Interactive REPL. In this part we are going explore building functions as a service (FaaS) components, more specifically with AWS Lambda. The following text will assume that you are familiar with what AWS Lambda is and have some experience with it.
F# for the Cloud worker In part 1 we got our feets wet with some initial simple Hello Cloud scripts, using F#. This was then expanded to do actual connectivity to AWS and list S3 buckets in an AWS account. In this part, we will sidetrack a bit into the topic of developer workflow and then continue with more exploration of AWS services and get a bit more into F#, with scripts to retrieve server information.