terraform-aws-lambda VS Projects

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

Now that I had decided on setting up Bitwarden, I had to build an AWS environment to run it on. I decided to do this in Terraform, as it lets me document Infrastructure-as-Code, and makes it easy to set up and tear down. I've put all of the code needed with instructions and minimal tweaks in this Github project folder for others to use as well, if it is helpful.

Here is a project I did where I included the Python code, and got Terraform to zip the code and upload to Lambda. I did create the Lambda Layer manually with all the dependencies though.

Add it to the API Gateway Stage. Here is my Terraform code on how I did it. You should be able to add it manually though under Access Log Settings. More info in this article.

Here's an example from a project I did that may help. You'll need:

The README.md on the Github page is also extremely detailed, so I'd recommend reading through that as well.

I'd also recommend adding some print statements to your Lambda function so the data shows up in Cloudwatch. You can see how I did this here. I added some specific cases and responses (and I used print statements for debugging in CloudWatch). Instead of just return fizz, add multiple cases, status codes, and print log lines so they show up in CloudWatch.