s3_website VS aws-lambda-go-api-proxy

For my personal site, which is 10 years old, I use Middleman, and I deploy the site to S3/Cloudfront with s3_website. It works fine for now. If s3_website stops working, I'll move to Netlify probably.

resource "aws_cloudfront_distribution" "frontend" { enabled = true aliases = ["${var.subdomain_name}.${var.domain_name}"] is_ipv6_enabled = true // cheapest: https://github.com/laurilehmijoki/s3_website/issues/150 price_class = "PriceClass_100" default_cache_behavior { allowed_methods = ["GET", "HEAD", "OPTIONS"] cached_methods = ["GET", "HEAD"] target_origin_id = var.frontend_s3_origin_id viewer_protocol_policy = "redirect-to-https" default_ttl = 0 max_ttl = 0 forwarded_values { query_string = false cookies { forward = "none" } } } origin { domain_name = var.frontennd_s3_origin_domain_name origin_id = var.frontend_s3_origin_id custom_origin_config { http_port = 80 https_port = 443 origin_keepalive_timeout = 5 origin_protocol_policy = "http-only" // setting defined after terraform import. can try with https-only origin_read_timeout = 30 origin_ssl_protocols = ["TLSv1", "TLSv1.1", "TLSv1.2"] } } restrictions { geo_restriction { restriction_type = "none" } } viewer_certificate { acm_certificate_arn = aws_acm_certificate_validation.default.certificate_arn cloudfront_default_certificate = false minimum_protocol_version = "TLSv1.2_2019" ssl_support_method = "sni-only" } } resource "cloudflare_record" "frontend_service" { name = "${var.subdomain_name}.${var.domain_name}" value = aws_cloudfront_distribution.frontend.domain_name type = "CNAME" proxied = true zone_id = lookup(data.cloudflare_zones.default.zones[0], "id") }

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