Open Source .NET Core Lambda Runtime

[normj]

This issue is to track the effort in the amazon-lambda-runtimesupport branch which introduces a new NuGet package called Amazon.Lambda.RuntimeSupport that can be used for user provided .NET Core runtimes to Lambda. Example usage of this is to publish .NET Core 2.2 or .NET Core 3.0 preview Lambda based functions.

[normj]

Current status is the library is going through CR. Additionally tooling is being worked on to support this. Initially plans is to have the Amazon.Lambda.Tools support .NET Core self contained deployment as the way to get the .NET Core runtime bits Lambda.

[andymac4182]

If I am reading this correctly we can use the Amazon.Lambda.RuntimeSupport nuget with the existing libraries and it will support self contained deployment? I would love to be able to support .NET Core 3 Web App deployment behind an ALB.

Potentially would it be worth creating some middleware to transform from the API Gateway / ALB Event representation into normal headers and body to allow kestrel to do the rest?

[vellozzi]

Just released Amazon.Lambda.RuntimeSupport

[DeniseJames]

Where may I find a Visual Studio NET 2.1 walkthrough using the S3 proxy. I am brand new to using AWS. I got my front and back end to work on my computer. I successfully uploaded the front end in an S3 bucket and host at my new domain, goop.dev

[vellozzi]

Amazon.Lambda.RuntimeSupport isn't meant to be used for .NET Core 2.1 lambda functions. For 2.1 you should use the built-in runtime.

It sounds like your question may be better as its own GitHub issue. I'm not sure what you mean by the S3 proxy.

Can you open a new issue and give some more detail? Open it in this repo if it's Lambda-related, or in https://github.com/aws/aws-sdk-net if it's related to the .NET SDK.

[normj]

Closing as the feature has shipped

[DeniseJames]

Thanks vellozzi. I will open my first issue.

[RoyiNamir]

@normj So now we can use 2.2 in our lambda when publishing?

But what about the Mock Lambda Test Tool ? in 2.1 projects all is ok.

But in 2.2 we get a bizarre error #478