terraform-aws-lambda VS serverless-graphql

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

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless