terraform-aws-security-group VS terraform-aws-lambda

I've got a terraform workspace that has grown very organically. I'm setting my security group rules in a locals definition then calling each type of rule from each of the local values. I've looked into the security group module by Anton but because we have a mixture of CIDRs and Secgroups (as destinations and sources) I do not believe we can leverage it the way it is intended to be.

First of all, I don't much go for stuff like https://github.com/terraform-aws-modules/terraform-aws-security-group, I find it obscures what's actually going on. Where before I just had to learn how AWS works, now I have to learn how AWS and all of these external modules work. Remember, infra-as-code isn't the same as other code-code, the same approaches that work for code-code don't always work for infra-as-code.

Looks good, but there is no such rule named "splunk" but there are 4 of them - https://github.com/terraform-aws-modules/terraform-aws-security-group/blob/master/rules.tf#L139-L142 .

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