aws-lambda-go-api-proxy VS tflint

I really like the extensibility of LangChain. While I understand that langchaingo may not be as popular as the original python version (I hope it will reach there in due time 🤞), but it's nice to be able to use it as a foundation and build extensions as required. Previously, I had written about how to use the AWS Lambda Go Proxy API to run existing Go applications on AWS Lambda. The AWS Lambda Web Adapter offers similar functionality but it has lots of other benefits, including response streaming and the fact that it is language agnostic.

A frustration shoutout to the aws maintainers that are ignoring PRs that enhance the usability of their services... even for over a year. https://github.com/awslabs/aws-lambda-go-api-proxy/pull/136

Check out https://github.com/awslabs/aws-lambda-go-api-proxy. It will allow you to run gin (or other http servers) in lambda.

For REST APIs, I create standard Go HTTP handlers, and use a library like https://github.com/a-h/awsapigatewayv2handler (mine, for API Gateway V2 only), or AWS's https://github.com/awslabs/aws-lambda-go-api-proxy or github.com/akrylysov/algnhsa to convert from Lambda handlers to standard Go HTTP handlers.

Hey I liked this post, seems really nice. I used Golang for an API in my current work, I used the gorillamux with this library https://github.com/awslabs/aws-lambda-go-api-proxy. It wraps the API into the APIGateway Proxy. You can use it too if you want to create a small API, there are examples with cloudformation there.

using {proxy+} on api gateway, route handler needs to be included. People should consider using github.com/awslabs/aws-lambda-go-api-proxy (with gin or mux)

This does something similar: https://github.com/awslabs/aws-lambda-go-api-proxy

As you can see, we defined that any path and method can trigger our lambda over API Gateway that we had previously created. With this approach and with using this solution with the Go Echo framework, we reduced the number of lambdas (also with this approach we solved the problem with a hard limit of total size that all lambdas can have). Using the aws-lambda-go-api-proxy with echo framework we defined a REST controller that is managing real paths and methods that our lambda consumes.

For our example which use the Go Gin framework, to minimize the changes we could also use the great AWS Lambda Go API Proxy. You can find an example of lambda function in the article repository

AWS actually provides wrappers for most HTTP handler functions in their adapter package: https://github.com/awslabs/aws-lambda-go-api-proxy

‍TFLint is a Terraform linter focused on possible errors, best practices, and style conventions in your Terraform code.

TFlint is a powerful linter for Terraform, designed to catch errors and issues that terraform plan may not detect. As Terraform grows in popularity for infrastructure as code, the need for robust tools to ensure code quality and reliability becomes paramount. TFlint fulfills this need by analyzing Terraform configurations to find problems that are not covered by syntax checks. It checks for things like unsuitable AWS instance types, incorrect IAM policy syntax, and the use of deprecated syntax or features. By integrating TFlint into the development process, users can proactively identify potential problems, improving the stability and efficiency of their infrastructure deployments. This additional layer of validation is crucial for maintaining high standards in complex, cloud-based infrastructures.

Looking at the description, https://github.com/terraform-linters/tflint , I think it's not what I am looking for. The reason I used a different tcp port is to make the health check on load balancer fail. It's also the same as not changing the tcp port but developer making a code change in their javascript, nodejs, java, etc fail to start properly. If that happens, load balancer's health check will fail as well.

TFLint is an open-source infrastructure as code linter tool that helps developers and DevOps teams identify potential issues and errors in their Terraform code by checking the Terraform configuration files for best practices, coding standards, and policy compliance.

Indeed, that is the case, atm. Your comment got me searching a little bit more. It seems that they are planning to implement a flag for small fixes https://github.com/terraform-linters/tflint/issues/266

Sounds like tflint to me!

I created a .tflint.hcl with the following content: https://github.com/terraform-linters/tflint/blob/master/docs/user-guide/config.md (The example)

TFLint: This is a Terraform linter that checks for errors and best practices in your Terraform code. TFLint helps to catch common mistakes, such as variable name clashes, missing required variables, or invalid resource arguments. It also checks for compliance with best practices, such as naming conventions and resource ordering. By using TFLint, you can catch errors early on, which helps to improve the quality of your Terraform code.

tflint: Linter para Terraform, serve para avisar sobre problemas com sintaxe, erros nos principais provedores de nuvem, garantir boas práticas e outras coisas.