Explore >> Select a destination
|
You are here 
|
beeb.li | ||
| | | | |
thinkingeek.com
|
|
| | | | | AWS Lambda is one of those technologies that makes the distinction between infrastructure and application code quite blurry. There are many frameworks out there, some of them quite popular, such as AWS Amplify and the Serverless Framework, which will allow you to define your Lambda, your application code, and will provide tools that will package and provision, and then deploy those Lambdas (using CloudFormation under the hood). They also provide tools to locally run the functions for local testing, which... | |
| | | | |
www.hugozap.com
|
|
| | | | | A collection of random notes about life | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | In my previous post I showed how to build a .NET 5 library inside a docker image and deploy it to an AWS Lambda. This post is a small extension on that. I'm going to build a .NET 5 Web API application, turn it into a docker image, deploy it to an AWS Lambda, and connect an API Gateway to the Lambda to call the controller inside the application, inside the container, inside the Lambda! | |
| | | | |
gist.github.com
|
|
| | | Google Kubernetes Engine manifest for Workload Identity using Google Cloud IAM - gke_iam.yaml | ||
