Cannot deploy a self-contained .NET Core 3.0 application to AWS Lambda

After digging through the source code of the Amazon Lambda Dotnet CLI tools here: https://github.com/aws/aws-extensions-for-dotnet-cli/blob/6b3c0eaf04bb62995ca1c5dd71b0db7e564e8b74/src/Amazon.Lambda.Tools/LambdaDotNetCLIWrapper.cs)

I found the following code that builds the dotnet publish command:

// If you set the runtime to RUNTIME_HIERARCHY_STARTING_POINT it will trim out the Windows and Mac OS specific dependencies but Razor view precompilation
// will not run. So only do this packaging optimization if there are no Razor views.
if (Directory.GetFiles(fullProjectLocation, "*.cshtml", SearchOption.AllDirectories).Length == 0)
{
    arguments.Append($" -r {LambdaConstants.RUNTIME_HIERARCHY_STARTING_POINT}");

    if (msbuildParameters == null ||
        msbuildParameters.IndexOf("--self-contained", StringComparison.InvariantCultureIgnoreCase) == -1)
    {
        arguments.Append(" --self-contained false ");
    }

    if (string.IsNullOrEmpty(msbuildParameters) ||
        !msbuildParameters.Contains("PreserveCompilationContext"))
    {
        _logger?.WriteLine("... Disabling compilation context to reduce package size. If compilation context is needed pass in the \"/p:PreserveCompilationContext=false\" switch.");
        arguments.Append(" /p:PreserveCompilationContext=false");
    }
}

My site did indeed include a CSHTML since it was a full-stack web app. Adding the following parameter to the msbuild parameters fixes the issue: -r rhel.7.2-x64

But AWS Lambda is not meant to handle full stack applications and static files won't serve properly, so best bet is to break up the application so that the Asp.Net Core lambda project is just a pure API.