chalice VS aws-lambda-dotnet

That looks similar to Chalice (also for Python)

https://github.com/aws/chalice

AWS Chalice

It’s not terraform but there’s a wonderful aws framework for lambda called Chalice.

I'm working with AWS Chalice. It's a Python framework that deploys to lambdas, though it has its share of quirks/issues.

Check out Chalice -- it's Flask-y by design but integrates natively with AWS's serverless stack.

I'm using pip 22.1.2 and according to this post, this issue should've already been solved. Anyone that help me with this? Thanks.

There's a framework similar to Flask that makes it easy called Chalice.

I saw this issue: https://github.com/aws/aws-lambda-dotnet/issues/245

Creating Lambda Project using Amazon.Lambda.Templates. I use Amazon.Lambda.Annotations because it will be similar to my previous console program, and we can use dependency injection.

Hopefully, this post will have intrigued you enough to check out the new framework, and try converting some of your existing functions into what I think is a much more readable and easier to comprehend format. Also, the development team is always interested in feedback, which you can supply in the issues folder of their repo. You can also find the design document for the annotations in this issue.

I don't think it's exactly what you're looking for, but you could try out the LambdaTestTool https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool

According to this GitHub issue we need to add and configure an additional package when running a custom runtime on ARM:

I'm assuming API's are REST APIs. Those sound like excellent use cases for running as Lambda functions. If the API's are an ASP .NET Core Web API project it is possible to deploy that to Lambda using the Amazon.Lambda.AspNetCoreServer, https://github.com/aws/aws-lambda-dotnet/tree/master/Libraries/src/Amazon.Lambda.AspNetCoreServer, NuGet package. That can be a quick way to get something working and then later choose to rearchitect to a smaller more micro services architecture if necessary.

AWS provides a NuGet package (see Amazon.Lambda.AspNetCoreServer) that makes it easy to do this. It works pretty well, but instead of one copy of the API serving many clients you have many copies of the API each serving one client at a time. There are also limitations in areas like file upload and download (which vary depending upon whether this is being used with API Gateway or an Application Load Balancer).