aws-sam-cli VS aws-lambda-go-api-proxy

aws-sam-cli-linux

Does anyone have any success with API Gateway/Lamba for local environment with hot-reloading? I was playing around with “sam local start-api” a few weeks ago with along with CDK but it doesn’t seem like hot-reloading is supported, and need to manually restart for code changes to reflect, which is currently stopping me from trying out the API Gateway/Lamba combo further due to inefficient DX. Here’s a GitHub issue about it: https://github.com/aws/aws-sam-cli/issues/901

Mostly due to lack of proper documentation it was difficult to get the HTTPApi syntax correct. The yaml file is very picky for CORS configuration on an HTTPApi. Luckily I found this github issue which allowed me to troubleshoot my yaml file.

No, it's not just muscle memory. It doesn't work with podman. That's what I'm talking about https://github.com/aws/aws-sam-cli/issues/1668

AWS SAM CLI with the support of Typescript is still in Beta. If you want more advanced features maybe you should not use it. Lately, in version 1.49.0 External and Loader properties have been added. If you want to share your feedback and/or requests this issue has been created.

I spent a while creating a custom runtime to use the native-image agent to harvest config from my Lambda, and then patching sam cli to work in Docker user networks... after pushing through all that, I still didn't get a working build - the native-image compiler just doesn't support everything (or didn't support my feature set, at the time - there has been a new release since then). In my case I think it was Guice that defeated me.

SAM support for TypeScript has been lagging for some time, but a pull request was just merged that should change that. It looks like we'll be able to add an aws_sam key in the package.json file to enable building within the SAM engine as part of sam build. Although this PR has been merged to aws-lambda-builders, the engine behind sam build, it will still need to be added to aws-sam-cli and released (to much fanfare, one expects) before it can be used with SAM.

I am installing SAM CLI on windows and its super simple. All I need to do is Click on this MSI installer.

sem-version java 8 wget https://github.com/aws/aws-sam-cli/releases/latest/download/aws-sam-cli-linux-x86_64.zip unzip aws-sam-cli-linux-x86_64.zip -d sam-installation sudo ./sam-installation/install checkout cd java-app-backend cache restore build-java-app-backend-$SEMAPHORE_GIT_BRANCH sam deploy --no-confirm-changeset --stack-name serverless-web-application-java-backend --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM

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