gofaas
gofaas copied to clipboard
nzoschke
A boilerplate Go and AWS Lambda app. Demonstrates an expert configuration of 10+ AWS services to support running Go functions-as-a-service (FaaS).
The [docs](https://github.com/nzoschke/gofaas/blob/master/docs/lambda-at-edge-oauth.md#aws-config) about private static websites show a bucket configuration that implies usage of the website endpoint (`WebsiteConfiguration`): ```yaml Resources: WebBucket: Properties: BucketName: !Ref WebDomainName WebsiteConfiguration: ErrorDocument: 404.html IndexDocument: index.html...
See https://github.com/awslabs/aws-sam-cli/releases/tag/v0.6.2 ```shell $ brew tap aws/tap $ brew install aws-sam-cli ``` ```shell $ pip uninstall --user aws-sam-cli $ pip3 uninstall --user aws-sam-cli ```
A custom resource appeared in #67 to toggle API Gateway tracing. It would be good to document how this works with Go and Lambda.
We can lift the JWTClaims helper out of our handler functions and into an API Gateway Authorizer, further reducing application code and increasing security. Support for this in SAM is...
Consider exploring the caching feature of API gateway: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-caching.html
It would be nice to support and document debugging Go apps. However it looks like it might not work upstream yet: https://github.com/awslabs/aws-sam-local/issues/281
Wishlist
What are the things that still feel painful to you and that you hope AWS fixes in the next 6-12 months?
It'd be interesting to demonstrate how to use DDB autoscaling to provision a 1,1 table but that could burst to 10x throughput without any management from the ops side of...