terraform-provider-openfaas VS terraform-aws-lambda

Alex, OpenFaaS founder here. The author has done a huge amount of work here, I am surprised that it's being given away for free, and not being monetized (it should be).

I often hear folks complain that Kubernetes is complex, and hard to understand. We've done a lot of work to make the experience of deploying functions simple on K8s, with very little to manage. But it still costs you a K8s cluster.

We created a new of openfaas called "faasd" which can run very well somewhere like DO or Hetzner for 3 EUR / mo. It doesn't include clustering, but is likely to be suitable for a lot of folks, who don't want to get deep into IAM territory.

The REST API for OpenFaaS has a terraform provider that works with either version - https://github.com/ewilde/terraform-provider-openfaas

And there's a guide on setting up faasd with TLS on DigitalOcean, it took about 30 seconds to launch, and makes building functions much simpler than Lambda. "faas-cli up"

https://www.openfaas.com/blog/faasd-tls-terraform/

If I were going to use Lambda, the author's examples are probably what I would turn to, but there are other ways and it needn't be this complex.

There are just too many required parameters to create a single handler. And then you need to do that N times for each handler. Take a look at a complete Terraform example for a lambda: https://github.com/terraform-aws-modules/terraform-aws-lambd...

For a personal project it's just a bit much in my experience, especially since most personal projects can easily be served by a t3.micro.

https://github.com/terraform-aws-modules/terraform-aws-lambda/ - this modules has it all. There are various examples and submodules in that repository to help you achieve all your serverless tasks the same way.

It’s also weird not to know about terraform modules. There are a lot of things you _can_ configure because there are a lot of things people need to configure but if you’re using something like https://github.com/terraform-aws-modules/terraform-aws-lambd... it’s only a couple of lines of config for a Lambda.

I use the Community Terraform Lambda Module to define the lambda. It allows me to define a lambda in just a few lines that are configured with a role and can also be easily extended with policies. The cool thing is that cdktf supports a type import. To do this, simply add the following module to the cdktf.json file:

As somebody already mentioned in the comments, you can use the terraform-aws-lambda module as well as many other modules for typical serverless services like API Gateway v2, AppSync, EventBridge, StepFunctions, AppConfig, DynamoDB, and many more.

You can containerize the lambda functions and when you deploy each lambda function, you can overwrite the CMD for each function in the resource block to match what you need. I'm doing something similar but only deploy 2 lambda functions which use the same source code but do very different tasks. I also strongly suggest you use the terraform-aws-lambda module since it will build out all related resources you need.

Have a look at this module: https://github.com/terraform-aws-modules/terraform-aws-lambda

I can't find any open issues on github or anyone asking for it other than in the modules that are provided. https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/128