serverless-dotnet-demo VS RdXmlLibrary

.NET Core can absolutely run on Lambda and API Gateway. Check out the demos: https://github.com/aws-samples/serverless-dotnet-demo/. While I haven't actually implemented an AWS API Gateway backed by .NET Core Lambdas with EF Core accessing an RDBMS, a quick internet search shows people using EF Core with Lambdas. Can you point to the documentation you found that said you that EF Core requires trimming? As to Gravitron, I assume you meant AWS Gravitron-processor-backed EC2 (sorry, I'm not that familiar with Gravitron)? Is this a hard requirement? Why do you care about Gravitron?

We actually added a NativeAot row here: https://github.com/aws-samples/serverless-dotnet-demo

Regarding EF.Core, I've seen example rd.xml templates and references in GitHub about AOT trimming. I've spent a few hours trying to get EF.Core 7 to work, including trying pre-compiled models, but keep running into errors like this:

Yes, please do. That's would be very practical. As shameless plug, I will share my attempt to collect Rd.xml for various .NET libraries. https://github.com/kant2002/rdxmllibrary . I think that NativeAOT in similar position as it was TypeScript and would require community effort to make rd.xml which works in every condition. But I see a way, how you can embed rd.xml inside AWS.SDK, and inject into build pipeline so nobody would know about them.