Need to replumb SignalR to use AWS WebSocket API Gateway

[genifycom]

In the AWS Lambda Environment, we cannot use SignalR because the connection will be dropped when the AWS Lambda Instance exits.

Azure runs the Azure SignalR service for this purpose https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-concept-internals

I would like to have something similar in AWS. The AWS WebSocket API Gateway can already manage the WebSocket connection but I need to replumb the SignalR code to allow the client and server to interact via the AWS WebSocket API Gateway.

This would, at a minimum, entail the function services.AddServerSideBlazor(); and endpoints.MapBlazorHub(); to allow Server side Blazor to communicate with the AWS WebSocket API Gateway. Then there will also be client code to communicate with the AWS WebSocket API Gateway.

The idea is to allow Server Side Blazor to take advantage of the pre-existing AWS WebSocket API Gateway and thus expand its scope in the AWS serverless environment.

I have not delved into the DotNet Core code directly before.
Can anyone point me to the person (or the code locations) to get started in this Quest?
Has anyone else tried this?